/WEB-INF/config/default/magnolia.properties has the base line set of properties, customized with settings found in /WEB-INF/config/[contextName]/magnolia.properties. That should give you a more complete picture. The default magnolia.properties has some decent comments. I haven't looked at the wiki pages lately so I don't know what's posted and how much of it really pertains to version 2.1.x.
On bootstrapping ... If you change your persistence on a running magnolia, you really need to export the existing repositories and clear out the repositories directory. Not doing that will cause problems because different persistence managers will have different ways of encoding and storing data. Plus the indexes generated by lucene will most likely be out of sync. After changing the persistence manager, place the exported files in the proper bootstrap directory replacing the original bootstrap files and restart. --David Salman Elahi wrote: >First of all thank you very much for your help...well that makes sense, >I have looked at /WEB-INF/config/magnoliaAuthor* (or whatever ur >instance name is)*. Magnolia.properties file define these attributes. >But I would highly appreciate if you could elaborate it as you mentioned >earlier that would help to completely understand the concept. > >So that means these values are overriden at run time in web.xml and we >don't need to do that manually anymore ? So I think it should also be >removed from Wiki under magnolia 3.0 and updated with the new >information, right? > >And onething more... Are there any problems if you use pre-bootstraped >magnolia bundle instead of using .war files while you have to change the >database backend to say MySQL or anyother etc. > >Regards, > >Salman > >-----Original Message----- >From: [email protected] [mailto:[EMAIL PROTECTED] >Sent: 28 February 2007 16:40 >To: [email protected] >Subject: Re: [magnolia-user] Author and Public have identical web.xml >files > >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 ----------------------------------------------------------------
