sberhan
Joined: 18/11/2008 12:13:29
Messages: 1
Offline
|
I hope this is the right place to ask a question. When chaining actions together, it seems the sticky-ness of the chained action is lost. Please see the example below:
loadActions in ApplicationManager:
select.jsp
FirstAction:
SecondAction:
display.jsp
Depending on the selected choice in the form, action chaining does not seem to work as expected:
With Choice 1: the consequence in the action configuration for the FirstAction is configured to chain to the SecondAction. However, in this case, even though the SecondAction is sticky since adhere is called when the counter is zero, the action state is not preserved across subsequent invocations. (The input and output filters work as expected).
With Choice 2: the consequence in the action configuration for the FirstAction is configured to forward the request instead of chaining which would preserve the state of the SecondAction across subsequent invocations, but unfortunately, does not preserve the input/output filters.
The expected result I’m looking for is for the counter to be incremented properly across multiple invocations and both Input Message and Output Message to be set as well.
I’ve looked into the implementation of the getAction() method in ActionConfig which states:
I see, as an example, the SingleInstanceActionConfig, but there doesn’t seem to be another subclass of ActionConfig that would work. Please let me know if there’s a workaround. Thanks for reading this far
Thanks for your time,
Siraj Berhan
|