Hi Gavin,

As long as you don't change the PM configuration (the files in 
config/repo-conf/jackrabbit* ) and the Magnolia configuration (files in the 
config/*/magnolia.properties)
the webapp should just connect back to mysql w/o any issues.

HTH,
Jan

On Dec 14, 2010, at 4:05 PM, <[email protected]> <[email protected]> 
wrote:

> 
> hi there
> 
> I would like to try running Magnolia on Glassfish on MySQL (on Linux) - but 
> am having some problems.
> 
> I have seen the instructions at 
> http://wiki.magnolia-cms.com/display/WIKI/How+to+install+on+Glassfish but it 
> only talks about the authentication part.
> 
> What I am trying to do is take a copy of existing data from an install of 
> Magnolia (on Apache/Tomcat/MySQL/Linux) and redeploy to Glassfish - but 
> without losing all the work in the MySQL database.
> 
> I would really appreciate some instructions on the best way to do this.    
> 
> For example - the sorts of questions I have are - I assume should  use the 
> JBOSS bundled war file.  When I first deploy to Glassfish - I don't think I 
> have the luxury of editing the persistence manager settings - so Magnolia 
> defaults to Derby.  I can change these settings to mysql - but am not 
> convinced Magnolia is picking up my MySQL database - but suspect it is still 
> using the Derby db.  Is there a way to stop Magnolia (like there is in 
> Apache/Tomcat) - without having to stop Glassfish?
> 
> It might therefore be easier if someone has instructions on how to migrate 
> from Apache/Tomcat/MySQL/Linux to Glassfish/MySQL/Linux?
> 
> thanks in advance.
> 
> Gavin
> 
> 
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to