I know, it is possible to do this, but it's a bit more complicated, if only because the user's (developers, whatever) don't actually _see_ the backing map without opening up some stack method that provides access to the ThreadLocal. If we pass the context around, all that happens is that execute() -> execute(Map context).
Before anyone shoots this down, I really want you to look at the code that is in CVS. It's not that bad and it makes things much simpler -- which is a primary goal of XWork. I really think this new code is more powerful and much simpler than the existing WebWork core. If you check out the source (especially with DispatcherTest as well as deploy the war and access Foo.action -- same thing), you'll find that it's pretty appealing (IMHO). :) -Pat ----- Original Message ----- From: "Rickard �berg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 11, 2003 10:15 AM Subject: Re: [OS-webwork] Getting rid of thread locals > Patrick Lightbody wrote: > > ThreadLocal implies that you always have a single thread throughout the > > lifecycle of the action (prepare, execute, print results). This is true for > > a servlet container (single thread/request), but not so in other areas. > > No, it doesn't imply that. If the execution chain is broken, then one > simply takes the context and reuse it whenever the chain is restarted. > > /Rickard > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
