Jacek Wiślicki wrote:
Hi,
there was some time ago a thread on login pipeline and leaving
session attributes after calling invalidate() on a HttpSession object in
LogoutServlet. What about extending it with this code:
HttpSession session = request.getSession();
Enumeration attrNames = session.getAttributeNames();
while(attrNames.hasMoreElements())
session.removeAttribute(attrNames.nextElement().toString());
I'm not sure if it could have any influence on other portal components
or processes (maybe some attributes should be persistent?), but it seems
to work fine in my portal.
sounds useful, but maybe it should be optional for those of us using
other solutions
recommend creating a jira issue for it and provide a patch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
