[ http://issues.apache.org/struts/browse/WW-1421?page=comments#action_38170 ] Don Brown commented on WW-1421: -------------------------------
Yeah, while some of its settings could possibly be per package, most are definitely global and would take considerable work to change them. Also, if you take the path of a struts.xml per jar//module, you might not have one global config file everyone extends. Therefore, I really don't see how this idea could be implemented without a) being a huge source of confusion or b) taking a ton of work. For example, I created a ticket WW-1369 that had the goal of getting rid of all the globa/static elements of the framework, but as I dug into it, it proved just too large of a refactoring. Therefore, I think we should open up tickets for settings that we think could be changed to per-package, but close this ticket and leave the struts.properties file alone for now. > Move global settings from property file to Struts configuration > --------------------------------------------------------------- > > Key: WW-1421 > URL: http://issues.apache.org/struts/browse/WW-1421 > Project: Struts 2 > Issue Type: Improvement > Reporter: Ted Husted > Fix For: 2.0.1 > > > On 8/29/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote: > >> So we need to specify all these settings as > >> properties, or could they be specified in a > >> struts.xml instead? I > >> it would be nice if we could configure > >> everything in one place. > > > > Yes, I agree, we should do this. The only reason we had it split up before > > was because > > we didn't have a WebWork-specific DTD. But we have that now, thanks to Don, > > we I > > agree, we should change it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
