[
https://issues.apache.org/struts/browse/WW-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Brown resolved WW-1640.
---------------------------
Resolution: Won't Fix
Fix Version/s: (was: Future)
Or more accurately, "Can't Fix" :)
> When using JSP templates for tags, missing templates fail without error
> -----------------------------------------------------------------------
>
> Key: WW-1640
> URL: https://issues.apache.org/struts/browse/WW-1640
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - Tags
> Affects Versions: 2.0.1
> Environment: Tomcat 5.5, Mac OS X 10.4
> Reporter: Joe Germuska
> Priority: Minor
>
> A developer on my team set up his first Struts 2 app and set the Struts
> property
> struts.ui.templateSuffix=jsp
> He didn't understand the meaning of the property, so no corresponding
> templates were set up in the webapp path.
> The problem was that there were no error reports for this situation:
> In org.apache.struts2.components.Include
> String resourcePath = getContextRelativePath(request, aResult);
> RequestDispatcher rd = request.getRequestDispatcher(resourcePath);
> if (rd == null) {
> throw new ServletException("Not a valid resource path:" +
> resourcePath);
> }
> The RequestDispatcher was not null, even though this page did not exist. I
> was surprised by this, but in short, he and a teammate were baffled as to why
> these new tags just weren't working.
> I'm setting the priority of this to minor because JSP templates are not that
> common, and besides, I have no idea how you'd fix it if the RequestDispatcher
> doesn't complain when a path doesn't exist. Is this unique to Tomcat 5.5? I
> thought I'd document it and if anyone has some time, they can experiment to
> see if its a wider problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
