We have some fairly twisted logic around the login to our site (sometimes you have to fill out a login form, but sometimes you can hit a special URL which will automatically log you in) which is apparently no longer working the way it used to under Tapestry 3. Basically, in the pageBeginRender() of the Home page we want to be able to set a cookie and redirect to a different page (we accomplish this by using a PageRedirectException). It seems that the throwing of the PageRedirectException is throwing away the old HttpServletResponse and starting over. Thus our cookie never gets set.
My only thoughts are to put that cookie somewhere (in an ASO or Hivemind-injected service) and then pull it back out after the PageRedirectException has been handled, and writing it using that new response. Has anyone done anything like this before or can anyone point out a "better" way of handling this sort of situation? Regards, Bryan
