Hi again! >[...] >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? >
Thank you very much for your clarification. That was the missing link. So I really misunderstood the intention of this feature. That is really good news to the end of my working day, so I can now enjoy the evening. :) Thank you very much and have a nice day! Greetings from munich! Peter ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
