DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5368>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5368 StandardContextValve changes session state from new to old too late for other Valves [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomcat- | |[EMAIL PROTECTED] AssignedTo|tomcat- |[EMAIL PROTECTED] |[EMAIL PROTECTED] | ------- Additional Comments From [EMAIL PROTECTED] 2001-12-12 12:36 ------- Doing something like this makes sense to me. Implementing it would seem to involve the following: * Modify o.a.c.Pipeline to include a method that lets you stick a Valve at the head of the chain instead of the end. * Modify o.a.c.core.StandardPipeline to implement this * Modify o.a.c.startup.ContextConfig to add a new valve containing the session.access() call. Does this sound like a reasonable approach? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
