RE: [OS-webwork] in DefaultActionProxy.execute() whats the purpose of the nestedContext and WW-407?

2003-12-05 Thread Jason Carreira
The purpose is for each ActionInvocation to have its own ActionContext which is only active while the ActionInvocation is being executed (as managed by the ActionProxy). If, for instance, you chain to another Action, that nested Action should have its own ActionContext which is available while

Re: [OS-webwork] in DefaultActionProxy.execute() whats the purpose of the nestedContext and WW-407?

2003-12-05 Thread Francisco Hernandez
the tags work fine in sitemesh decorators as it stands, but the problem is that i need to use ActionContext.getContext().getSession() and that returns null when used inside of a sitemesh decorator Im using ActionContext.getContext().getSession() inside the decorator to do the typical checking of

RE: [OS-webwork] in DefaultActionProxy.execute() whats the purpose of the nestedContext and WW-407?

2003-12-05 Thread Jason Carreira
You could have it populate this boolean during execution, or pull this into an Interceptor. I don't think leaving around leftover state in a ThreadLocal is the way to go, though... -Original Message- From: Francisco Hernandez [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003

Re: [OS-webwork] in DefaultActionProxy.execute() whats the purpose of the nestedContext and WW-407?

2003-12-05 Thread Francisco Hernandez
I like that idea actually, moving this logic into an interceptor, but i still think ActionContext.getContext().getSession() should not be returning null when used in a sitemesh decorator. Jason Carreira wrote: You could have it populate this boolean during execution, or pull this into an