You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Jeromy Evans (JIRA)" <ji...@apache.org> on 2008/07/01 04:52:05 UTC
[jira] Created: (WW-2701) Codebehind unknown handler can't find
results in JAR
Codebehind unknown handler can't find results in JAR
----------------------------------------------------
Key: WW-2701
URL: https://issues.apache.org/struts/browse/WW-2701
Project: Struts 2
Issue Type: Bug
Components: Plugin - CodeBehind
Affects Versions: 2.1.2
Reporter: Jeromy Evans
Assignee: Jeromy Evans
Priority: Minor
Fix For: 2.1.3
The CodeBehindUnknownHandler searches for results using servletContext.getResource(path) and then ClassLoaderUtils.getResource(path, getClass()).
The path always has a leading slash as this is mandatory to find resources in the servlet context but the leading slash needs to be removed to load resources from jars.
The existing unit tests do not include the leading slash when searching the classpath so the small bug had slipped through.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WW-2701) Codebehind unknown handler can't find
results in JAR
Posted by "Jeromy Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeromy Evans resolved WW-2701.
------------------------------
Resolution: Fixed
Improved the unknown handler's use of leading slashes and path concatenation (include/omit slashes as appropriate).
> Codebehind unknown handler can't find results in JAR
> ----------------------------------------------------
>
> Key: WW-2701
> URL: https://issues.apache.org/struts/browse/WW-2701
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - CodeBehind
> Affects Versions: 2.1.2
> Reporter: Jeromy Evans
> Assignee: Jeromy Evans
> Priority: Minor
> Fix For: 2.1.3
>
>
> The CodeBehindUnknownHandler searches for results using servletContext.getResource(path) and then ClassLoaderUtils.getResource(path, getClass()).
> The path always has a leading slash as this is mandatory to find resources in the servlet context but the leading slash needs to be removed to load resources from jars.
> The existing unit tests do not include the leading slash when searching the classpath so the small bug had slipped through.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.