Not sure; can't tell by looking at the API docs. Probably, though.
Ultimately I'd like the property config names to be a path to a config object/property--some may already be, I haven't really started looking at those bits. I'd like the ability to define everything hierarchically, in one place, in a variety of ways (XML, Groovy, etc.) That's another reason I'm not sure that keeping the S2 config file as an XW2 config file suits me--S2 is a web extension to XW2, and I don't have a problem having S2-specific functionality in the config. (re: things like GET/POST differentiation as discussed in another thread). It may not matter, or not matter much. d. 2011/12/12 Łukasz Lenart <lukasz.len...@googlemail.com> > 2011/12/11 Dave Newton <davelnew...@gmail.com>: > > I'm fine with that; there is already a provider interface in > > XWork--not sure where the property file config comes from, haven't dug > > in. > > DefaultPropertiesProvider and LegacyPropertiesConfigurationProvider ;-) > > > A property file wouldn't work really well as a struts.xml replacement. > > I guess I just don't see the value in a properties file at this point. > > > > I was planning on doing a Groovy configurer like its > > ConfigurationSlurper (or whatever it's called) to better reflect the > > config param hierarchies, possibly merging it with the XML config, but > > haven't given it much thought yet. > > You mean something like WebApplication [1] in Wicket ? > Programmatically define config ? > > [1] > http://wicket.apache.org/apidocs/1.4/org/apache/wicket/protocol/http/WebApplication.html > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > Warszawa JUG conference - Confitura http://confitura.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
