> I don't want to put the whole configuration outside of the war, just
> a few properties.
>
> Like sampleDomains.xml:
> <beans>
> <bean id="projectDomains" class="java.util.HashSet">
> <constructor-arg index="0" type="java.util.Collection">
> <list>
> <value>cms-ontw-cocoon</value>
> <!--value>${cms.domain}</value-->
> </list>
> </constructor-arg>
> </bean>
> </beans>
>
> And then just the cms.domain inside a property file. I'm busy with a
> patch (the last one didn't work all the way down).
I am sorry but I really do not see an advantage to being able to
externalize a portion of the server manager configuration if the server
manager configuration is fully externalizable itself. You either have:
- the server manager configuration inside the WAR, which means that you
have to rebuild for each deployment, or
- the server manager configuration outside of the WAR, which means you
can deploy the same WAR on multiple hosts.
IMHO your changes will not improve either situation. I suggest you
create a separate SVN project for the server manager configuration (but
make sure you don't store any (plain text) passwords in it), and compile
the CMS with a configuration location outside of the WAR. You can then
simply deploy the server manager configuration from the SVN project to
any host.
Johan
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
