It seems include includes servlet's output
(copying stream data) and it's really not related to actions at all, while
Action tag uses actions to eventually dispatch to view components.
I hope that's a good time to make sure Pat remembers
my suggestions. IMHO Action tag executing results should push the action onto
the stack just before it does execute result, and then it should pop the action
off the stack as soon as result is finished.
This way you would (logically) access both
actions in the included view.
The problem was that action invocations was assumed
never take actions off the stack, but I posted apropriate patches to deal with
that.
Regards,
-- Mike
|
- [OS-webwork] ActionTag changes Jason Carreira
- Re: [OS-webwork] ActionTag changes Matt Ho
- Re: [OS-webwork] ActionTag changes Matt Ho
- [OS-webwork] release vs reset Matt Ho
- [OS-webwork] ActionTag changes John Patterson
- RE: [OS-webwork] ActionTag changes Patrick Lightbody
- RE: [OS-webwork] ActionTag changes Michal Mosiewicz
- RE: [OS-webwork] ActionTag changes Jason Carreira
- RE: [OS-webwork] ActionTag changes Jason Carreira
- Re: [OS-webwork] ActionTag changes John Patterson
- RE: [OS-webwork] ActionTag changes Patrick Lightbody
- Re: [OS-webwork] ActionTag changes John Patterson
- RE: [OS-webwork] ActionTag changes Patrick Lightbody