Peter Molnar <mpdev <at> nanasoft.hu> writes: Hi,
> For me, it seems logical to store it in the parent webapp created to > contain all blocks. Do blocks have access to the properties defined in the > parent application? Yes, they do. The properties in your parent webapp will override properties defined in the blocks. I like to put all properties for the acceptance testing and production environments in the parent webapp. This way the properties are all in one place. For development I use the blocks properties. > > Even so, installing configuration in there seems somewhat obscure when the > WAR is deployed on a web container. > The Cocoon configurator support running modes. This means properties placed in /cocoon/properties/dev will not be visible when the application is running in production mode (/cocoon/properties/prod is then used). This makes it possible to define properties for different running modes and just deploy the application. In each running mode the correct property values will be used. I don't have the need to change configuration this way once the application is deployed, because I configured the correct the values when building the WAR. Kind regards, Hubert Klein Ikkink --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
