Did you see this thread on the ML ?
http://news.gmane.org/gmane.comp.cms.magnolia.user/cutoff=5778

Seems like it is the exact same case.
To put it in a nutshell :

Changing the Persistance Manager after the repository was bootstraped is usually neither recommanded nor effective. In order to activate the change, you have got to make magnolia bootstrap. Here are some basic steps.

- Backup your website, configuration and documents repositories using the xml export servlets/pages. - Delete your old repositories folder (but make sure you backup your whole site first, of course). This will force a bootstrap, therefore force using the choosen persistance method from the get-go. - Replace your saved xmls in /web-inf/bootstrap/common (or re-import them later, as you prefer, there are various restoring strategies) - Relaunch your magnolia instances, and watch your databases fill (a 3-5 minute task on a fast box for a site the size of the Samples demo Wars provided with Magnolia).

Once again, read the (whole) thread sabout installing DataSourcePersManager and/or about backuping and restoring Magnolia instances.

Nice day to you,
G.

Le 14 déc. 06 à 20:15, Christian Sylvestre a écrit :

I am looking forward to use Magnolia for a fairly big web site and for
simplicity of management I would prefer to have the repository located in
MySQL.

I then follow the procedure describes in some posting to the user list on
how to change the persistence manager to the one from iorgagroup.com.

It seems to be working fine when I started Tomcat for the first time since
I could see those messages in the console:

INFO info.magnolia.jackrabbit.ProviderImpl ProviderImpl.java(init: 143)
14.12.2006 20:01:18  Loading repository at
C:\software\apache-tomcat-5.5.20\webapps\magnoliaAuthor\repositories \magnolia
(config file:
C:\software\apache-tomcat-5.5.20\webapps\magnoliaAuthor\WEB-INF \config\repo-conf\jackrabbit-mysql-search-mysql-p
ooled.xml)
WARN
com.iorgagroup.jackrabbit.core.state.db.DataSourcePersistenceManager
DataSourcePersistenceManager.java(checkSchema:1014) 14.12.2006 20:01:19
-    Schema not existing. Starting database objects creation using
mysql.ddl file...

So that looks fine, the tables have been created in MySQL.

However the tables are empty? Shouldn't the whole content of the
repository be created in MySQL?

And if I look at any of the workspace.xml files I can see this:
<PersistenceManager
class="org.apache.jackrabbit.core.state.db.DerbyPersistenceManager">

Shouldn't the persistence manager be the one I defined in my repository
configuration file?

Any help would be welcome.

Thanks,

Christian

Note; FYI I am using Magnolia 3.0.1, Java 1.5 and Tomcat 5.5


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to