[
https://issues.apache.org/jira/browse/WW-5463?focusedWorklogId=943874&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-943874
]
ASF GitHub Bot logged work on WW-5463:
--------------------------------------
Author: ASF GitHub Bot
Created on: 15/Nov/24 07:46
Start Date: 15/Nov/24 07:46
Worklog Time Spent: 10m
Work Description: lukaszlenart opened a new pull request, #1127:
URL: https://github.com/apache/struts/pull/1127
WW-5463
--
Issue Time Tracking
-------------------
Worklog Id: (was: 943874)
Remaining Estimate: 0h
Time Spent: 10m
> SiteMesh 3.2.1 does not resolve jsp path after Struts Filter
> ------------------------------------------------------------
>
> Key: WW-5463
> URL: https://issues.apache.org/jira/browse/WW-5463
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - SiteMesh
> Affects Versions: 7.0.0
> Reporter: Romain TM
> Assignee: Lukasz Lenart
> Priority: Major
> Fix For: 7.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello, I am trying to make Sitemesh 3.2.1 works with my project updated to
> Struts 7.0.0-M9 without success.
> Indeed, after StrutsFilter applies, the Servlet path contains the final jsp
> path as usual. However, because the _RequestPath_ is ridden by Sitemesh from
> the _FORWARD_SERVLET_PATH_ attribute (WabAppContext.java line 95),
> SiteMeshFilter uses the original path attribute (my struts action name)
> instead of the resulting jsp path. So the configured decorator for my jsp can
> not be resolved anymore (It uses to work with Sitemesh 3.0 and Struts 6.3)
> Is it a known issue or a wrong configuration on my side?
> I am using
> _org.apache.struts2.dispatcher.filter.StrutsPrepareAndExecuteFilter_ as
> Struts filter and _org.sitemesh.config.ConfigurableSiteMeshFilter_ as
> SiteMesh filter
> Thanks for your help
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
