I believe the new magnolia 3.0 distribution moved that issue to the
magnolia.properties files under WEB-INF/config/[contextNameHere]. Just
create a folder for each context you are deploying and then place a
magnolia.properties file in it customizing the deployment. I'd offer
more detail, but my main development system is busy at the moment. Take
a look at the contents of /WEB-INF/config -- should offer some insights
at any rate.
--David
Salman Elahi wrote:
Dear All,
A quick query... In wiki at page
http://www.magnolia.info/wiki/Wiki.jsp?page=HowToInstall (under magnolia
3.0)it says for setting up a public instance do the following steps:
1 Re-name a second magnolia.war to magnoliaPublic and place it in
/webapps/
2 Change magnolia.root in web.xml to magnoliaPublic.root.
3 Change application name in web.xml to magnoliaPublic.
4 Change all instances of magnolia.root in log4j.xml to
magnoliaPublic.root
But in new magnolia Bundles (without .war files... I didn't check .war
ones) both files are identical whereas in magnolia 2.1.5 these files had
these changes already.
Does somebody know... If this is a problem (and we have to do the above
steps)or its fine with the new magnolia 3.0+ architecture (having
identical web.xml files for both instances).
Best regards,
Salman
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
