My problem is with the custom request - I overrode the request.getSession() to return null for these requests. However this seems to make struts choke.
The reason I did this is that I think creating a session & then calling session.invalidate() in the filter is redundant. I wanted to avoid creating the session completely.
Then I can also use the test (session != null) for the logic in my action classes to prevent unnecessary processing.
Is the session permanently featured in struts internals? Am I obliged to have sessions, even if only for the duration of individual requests?
Adam
PS I did ask this on the tomcat list, so I suppose I'm cross-posting, but I didn't get any response so I'm presuming it was just OT.
--
struts 1.1 + tomcat 5.0.14 + java 1.4.2
Linux 2.4.20 RH9
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

