You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Jung Kwang Sun (JIRA)" <ji...@apache.org> on 2007/06/05 07:02:28 UTC

[jira] Created: (WW-1965) hopefully wildcard available for struts.configuration.files configuration

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


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.


[jira] Commented: (WW-1965) hopefully wildcard available for struts.configuration.files configuration

Posted by "Wes Wannemacher (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/struts/browse/WW-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42322 ] 

Wes Wannemacher commented on WW-1965:
-------------------------------------

Is this a dupe of ww-2210? I posted a patch in xwork (since it would be much easier to implement this in xwork) as xw-574.

> 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.


[jira] Resolved: (WW-1965) hopefully wildcard available for struts.configuration.files configuration

Posted by "Rainer Hermanns (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/struts/browse/WW-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer Hermanns resolved WW-1965.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.1.0
         Assignee: Rainer Hermanns

Fixed in xwork 2.1.0 

> 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
>            Assignee: Rainer Hermanns
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> 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.


[jira] Updated: (WW-1965) hopefully wildcard available for struts.configuration.files configuration

Posted by "Ted Husted (JIRA)" <ji...@apache.org>.
     [ 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.