Martin Schnyder wrote :

> Try to invalidate the servlet session only in your SignOut page. Have a
look
> at how it is done in the VLib example. In the beginResponse method of the
> Logout page the (VLib) engines logout method is called. This just sets a
> flag (killSession) in the engine. In the cleanupAfterRequest method, the
> engine then invalidates the session.


Hello Martin,

I tried what you suggested, but it still doesn't work.
I keep getting the IllegalStateException, this is most intriguing.
I just have about 2 months of Java experience but in the
following code

protected void cleanupAfterRequest(IRequestCycle cycle)
{
 if (killSession)
 {
  try
  {
   HttpSession session = cycle.getRequestContext().getSession();

   if (session != null)
    session.invalidate();
   }
  catch (IllegalStateException ex)
  {
     // Do nothing.
  }
 }
}

shouldn't the Exception be silently ignored?
I guess I will have to read "Thinking in Java" again.

I'm going to try to setup locally the Virtual Library Demo,
to see if the Logout works, I haven't done it before because
EJB's and associates are way out my league.

Thanks for your help.

Luis Neves


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to