Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
hmm, why do we have another mechanism for setting properties now?. can't we put
in all properties into WEB-INF/cocoon/properties?
This was actually my first implementation, but I think there is a
difference between properties which you might want to use for anything
and a mechanism for overriding the configuration of your beans. The
latter is also just for spring (and Avalon).
So we have:
WEB-INF/cocoon/properties - with any properties :)
WEB-INF/cocoon/spring/*.xml Spring bean definitions
WEB-INF/cocoon/spring/*.properties Spring bean configurations
The difference might be subtle but I think we should keep this separate.
But of course this is not carved in stone yet, so we can change it in
every way we can agree on.
I was asking because this doesn't support the different running modes, does it?
No, but it will soon :)
can we make a block out of cocoon's way of doing property handling so
one could use it in non cocoon projects?
--
Leszek Gawron, IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
