Dick Zetterberg wrote:
It would work since the context is set on a per thread basis, i.e. the association that is done when the <action> tag is run is still in place.Isn't it possible to get a problem even if you do all your work in actions, for example if you are doing some Model-1 coding? For example if you have an action that you call many methods on, in a page like: <ww:action name="'MyAction'" id="theAction"/>Later on in the page you decide to get some property from it: <ww:property value="@theAction/someMethod"/> If that method "getSomeMethod" would try to access the session in the ActionContext it would not find one, isn't that so? So for that to work you would have to end the action tag at the bottom of the page instead, right?
AFAIK.
/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
