----- Original Message ----- From: "Rickard Öberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 29, 2003 12:41 PM Subject: Re: [OS-webwork] ActionContext clarification > > The WebWorky way is to have all code that does stuff in actions, and in > that case you'd never have any problem. > > /Rickard >
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? Cheers, Dick [EMAIL PROTECTED] ------------------------------------------------------- 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
