[WW-3815] Dispatching after action phase renders with different stack/TextProvider

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.3.3
• Fix Version/s: 2.3.7
• Component/s: Plugin - Portlet
• Assignee: Johannes Geppert
• Reporter: Michael Menzies
• Created: 14/May/12 15:18
• Updated: 05/Nov/12 19:45
• Resolved: 15/May/12 06:35

Description

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