[
https://issues.apache.org/struts/browse/WW-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Husted updated WW-1965:
---------------------------
Fix Version/s: Future
Setting Fix Version to "future" for issues without a set fix version.
> hopefully wildcard available for struts.configuration.files configuration
> -------------------------------------------------------------------------
>
> Key: WW-1965
> URL: https://issues.apache.org/struts/browse/WW-1965
> Project: Struts 2
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.0.6
> Environment: eclipse 3.2 WTP
> tomcat 5.5
> java 1.5
> Reporter: Jung Kwang Sun
> Priority: Minor
> Fix For: Future
>
>
> I'm building the struts2 based framework in application development.
> Because this's a SI(System Integration) project and a lot of developers are
> involved, integration is critical issue.
> Whenever I integrated the each module(developed by struts2), I should edit
> the "struts.configuration.files" property of struts.properties. Of Course, I
> can get it by using struts-plugins.xml, or pre-include the all struts xml
> file of each module. And I'll do one of both.
> (But In a certain case, both can make a confusion to each module developers)
> In the case of spring framework, they permit the wildcard configuration about
> applicationContext XML file like following :
> <context-param>
> <param-name>contextConfigLocation</param-name>
> <param-value>
> classpath:applicationContext*.xml
> </param-value>
> </context-param>
> So, I think wildcard permitted struts XML configuration can be good options.
> Best Regards.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
