[
http://www.stripesframework.org/jira/browse/STS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter resolved STS-671.
----------------------------
Resolution: Fixed
This is related to STS-565. The root of the problem is that we often end up
with the ExecutionContext and ActionBean using two different ActionBeanContext
instances in the same request. To fix that, DispatcherHelper, after resolving
the ActionBean for the request, will then check to see if the bean's context
instance is different from the one in the ExecutionContext. If so, then it will
take the bean's context, copy the event name from the ExecutionContext to it
(normally null) and then pass it to ExecutionContext.setActionBeanContext().
> Existing ActionBeanContext retains old event name on forward
> ------------------------------------------------------------
>
> Key: STS-671
> URL: http://www.stripesframework.org/jira/browse/STS-671
> Project: Stripes
> Issue Type: Bug
> Affects Versions: Release 1.5.1
> Reporter: Ben Gunter
> Assignee: Ben Gunter
> Fix For: Release 1.5.2, Release 1.6
>
>
> When a forward is done to an ActionBean class that has already been
> instantiated, setContext(..) is not necessarily called for the new
> ActionBeanContext, by design. In cases where the new context is not passed to
> the ActionBean, the context retains old information, such as event name, that
> can lead to some baffling issues. The relevant information should be passed
> to the existing context in such cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
