[
https://issues.apache.org/jira/browse/WW-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johannes Geppert resolved WW-3349.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Assignee: Johannes Geppert
Solved with Commit 1096834
> Extension .jspf not recognized as JSP result-type
> -------------------------------------------------
>
> Key: WW-3349
> URL: https://issues.apache.org/jira/browse/WW-3349
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Convention
> Affects Versions: 2.1.8.1, 2.2.1
> Environment: Any
> Reporter: Christian Bockermann
> Assignee: Johannes Geppert
> Priority: Trivial
> Fix For: 2.3
>
>
> I make use of jsp templates and small fragments, ending with .jspf
> These should be considered as result-type "dispatcher" as well (it seems that
> currently only jsp, jspx are considered to dispatcher-results)
> According to
>
> http://java.sun.com/developer/technicalArticles/javaserverpages/code_convention/
>
> the ending .jspf might be an option for jsp-fragments. Should this be added
> to ConventionsServiceImpl ?
> From ConventionsServiceImpl:
> /**
> * {@inheritDoc}
> */
> public Map<String, ResultTypeConfig>
> getResultTypesByExtension(PackageConfig packageConfig) {
> Map<String, ResultTypeConfig> results =
> packageConfig.getAllResultTypeConfigs();
> Map<String, ResultTypeConfig> resultsByExtension = new
> HashMap<String, ResultTypeConfig>();
> resultsByExtension.put("jsp", results.get("dispatcher"));
> // Added to make jspf a valid JSP-extension:
> resultsByExtension.put("jspf", results.get("dispatcher"));
> ....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
