On the table is the ThreadLocal issue and how to re-introduce it. The current Xwork code uses an ActionInvocation which is passed to each of the interceptors and holds the state of the request processing. In order to make Actions (more) backward compatible in WW 2.0, we need to re-introduce the ThreadLocal state management concept from WW 1.2/1.3.
Rickard, etc. let me know if this is a good time for you. Anyone who plans to attend, please look through the sandbox code first. If you have any other issues you'd like to discuss, please post them to this list so people have time to think about them beforehand. Patrick has suggested we do this on #xwork on irc.werken.com, so that it can be logged at http://irc.werken.com/channels/. Jason -- Jason Carreira Technical Architect, Notiva Corp. phone: 585.240.2793 fax: 585.272.8118 email: [EMAIL PROTECTED] --- Notiva - optimizing trade relationships (tm) ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
