For us the most ideal situation is to deliver one war file and one (external)
properties file, to configure all properties that can differ between
environments(DTAP, Development, Testing, Acceptance and Production). All
Operations want is to say, the URL for this external system is on one
environment http://testing.example.com and on another environment
http://production.example.com. Also for the domain, this can differ between
environments, ie. cms-acc-cocoon and cms-test-cocoon.
It is much easier for Operations to just change it in one place, and all in one
place. They don't have to change any other configuration, because that should
stay the same during the DTAP.
That's why we want to externalize those properties.
Is this an unusual use case?
With regards,
Nick Stolwijk
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Johan Stuyts
Sent: Wed 1/16/2008 8:49 AM
To: Hippo CMS development public mailinglist
Subject: RE: [HippoCMS-dev] Reading domainnamein
sampleDomains.xmlfrompropertyfile
> 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
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
