I'll take a shot at this since I wrote the article you are citing....
Maybe you're looking at this from the wrong perspective. The feature
was designed so that from a single build environment, you could create a
war file that can be deployed under different names and take on
different configs based on it's name. For instance, if your favorite
build environment puts together magnolia.war and you renamed it
magnoliaAuthor.war for deployment, it would take on the config from
WEB-INF/config/magnoliaAuthor/magnolia.properties. This eliminates the
need to have two separate projects to build two separate .war files with
the only difference being some minor setting changes that used to be
stored in WEB-INF/web.xml.
Does that clear things up some?
--David
Peter Götz wrote:
Hi Fabrizio,
thank you for your answer.
[...]
this is not suggested, unless you move all the tmp, cache, log
and repositories folders outside the webapp. You cannot run 2
instances of magnolia that share those folders. I suggest to
keep two exploded war, just unzipping two copies of the same
war in two different locations (like webapps/magnolia-author and
webapps/magnolia-public)
But I don't understand, why this form of configuration then makes sense, after all the little howto under http://magnolia.sourceforge.net/30/config/multiconfig.html says suggests right that. I can have one war, create two folders under WEB-INF/config for my configs and have both of my configurations managed by it.
Could anybody please explain me for what reasons I can do the above mentioned?
Thanks a lot!
Peter
fabrizio
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
