Title: Message
Looks like it.  I'll create a Jira issue.  As far as I can tell, the ServletDispatcherResult looks for a PageContext in the ActionContext.  If it finds it then it does an include instead of a forward.  But is is not finding it.
----- Original Message -----
Sent: Monday, December 15, 2003 3:52 PM
Subject: RE: [OS-webwork] ActionTag with executeResult

I don't understand... is this a bug?
-----Original Message-----
From: John Patterson [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 10:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] ActionTag with executeResult

WW2.  I have switched back to using a modified (non-caching) IncludeTag.  I think the problem was due to the ServletDispatcherResult not finding the PageContext in the ActionContext.
----- Original Message -----
Sent: Monday, December 15, 2003 1:52 PM
Subject: RE: [OS-webwork] ActionTag with executeResult

Is this WW1 or WW2?
-----Original Message-----
From: John Patterson [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 6:43 AM
To: Webwork
Subject: [OS-webwork] ActionTag with executeResult

Hi,
 
I am having problems using the ActionTag to compose my page of smaller bits.  Previously I had used the IncludeTag to do this.  The ServletDispatcherResult is doing a Forward instead of an include.
 
John.

Reply via email to