[
https://issues.apache.org/jira/browse/WW-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276818#comment-13276818
]
Michael Menzies commented on WW-3815:
-------------------------------------
Ah, found it. Ya, the new snapshot does the trick. Thanks.
> Dispatching after action phase renders with different stack/TextProvider
> ------------------------------------------------------------------------
>
> Key: WW-3815
> URL: https://issues.apache.org/jira/browse/WW-3815
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Portlet
> Affects Versions: 2.3.3
> Reporter: Michael Menzies
> Assignee: Johannes Geppert
> Priority: Minor
> Fix For: 2.3.5
>
>
> This is actually a rather old bug that was fixed in 2.1.3, but for some
> unknown reason the bug was reintroduced in 2.3.3.
> The PortletStateInterceptor merges the old stack with the current stack
> during the render stage. It should add the old root to the beginning of the
> current root. In 2.3.3 it now adds it to the end.
> This puts the DefaultTextProvider above the Action class, which breaks a
> bunch of struts tags if your action implements TextProvider.
> Unless there is a reason for the change, the simple fix is changing
> root.addAll(oldRoot); to root.addAll(0, oldRoot);
> I had created a stackoverflow question that explains the issue in detail.
> http://stackoverflow.com/questions/10557124/possible-struts-portlet-2-3-3-bug-action-class-not-at-the-top-of-the-value-stac
> Original bug:
> https://issues.apache.org/jira/browse/WW-2720
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
