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,
2011/12/9 Martin Cooper :
> We used to post the test build, announce it, wait for a week to give
> people some time to try it out, and then call the vote, since the vote
> is time-limited. Did we stop doing that at some point, and only give
> people 3 days (i.e. the duration of the vote) to test no
The Vote passed with result:
[X] General Availability (GA)
5 x +1 binding
2 x +1 non-binding
Thanks & Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
W dniu 9 grudnia 2011 08:02 użytkownik Łukasz Lenart
napisał:
> [X] General Availability (GA)
+1 binding
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
-
2011/12/11 Dave Newton :
> 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.xm
All tests in current projects passed.
+1 binding
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[x] General Availability (GA)
cheers,
Rainer
Rainer Hermanns
aixcept
Willibrordstraße 82
52134 Herzogenrath - Germany
w: http://aixcept.de/
t: +49 - 2406 - 979 22 11
f: +49 - 2406 - 979 22 13
m: +49
