[
https://issues.apache.org/jira/browse/WW-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940710#comment-13940710
]
Brandon Ramirez commented on WW-3330:
-------------------------------------
The fix for this issue seems to cause a regression for us.
After upgrading from Struts 2.1.8.1 to 2.3.16.1, this bug started affecting us.
Using the SiteMeshFilter, s.action includes work in FreeMarker templates
except for FreeMarker templates that are included via sitemesh. Switching to
FreemarkerPageFilter (a sub-class of SiteMeshFilter), which includes the fix
for the issue described here (WW-3330) swaps it so that s.action does not
render results unless it is included via sitemesh.
Is this intentional? If so, which configuration is proper?
I am unsure of this issue should be re-opened of if this should be considered a
separate issue. Please advise.
I realize it's unusual to have a mixed configuration such as this. We are
prepared to refactor whatever code we need to in order to upgrade, but I am
unsure which is the right direction to go.
> <@s.action> broken in sitemesh freemarker decorator page
> --------------------------------------------------------
>
> Key: WW-3330
> URL: https://issues.apache.org/jira/browse/WW-3330
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - SiteMesh
> Reporter: zhouyanming
> Assignee: Lukasz Lenart
> Priority: Blocker
> Fix For: 2.2.3
>
> Attachments: WW-3330-1.patch, WW-3330-2.patch, WW-3330.patch,
> testsitemesh.zip
>
>
> broken since this patch https://issues.apache.org/struts/browse/WW-3291
> <div id="left"><@s.action name="left" executeResult="true" /></div>
> <div id="content">${body}</div>
> <div id="right"><@s.action name="right" executeResult="true" /></div>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
