[MAGNOLIA-3475] Unable to update Magnolia WAR file w/ MySQL repo setup Created: 20/Dec/10 Updated: 21/Dec/10 Resolved: 21/Dec/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Douglas Kadlecek | Assignee: | Boris Kraft |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I have a custom war file with some custom modules that we are using for our website. I want to use MySQL as our content repo and maintain the data in the repo across new war file deployments to tomcat. Hovever, whenever I try to deploy a new war, I get java errors during magnolia startup. Here is the first one (al are similar referring to indexing the repo): 2010-12-20 09:58:31,841 ERROR org.apache.jackrabbit.core.RepositoryImpl : Unable to initialize workspace 'website' Recreating the Magnolia (blank) schema corrects the problem, but of course we want to keep the content of the db across war deployments. Is this possible? |
| Comments |
| Comment by Magnolia International [ 21/Dec/10 ] |
|
Hi, Yes, it is possible, but you need to set the repositories folder outside of your webapp. (using the magnolia.repositories.home property) This Jira project is used to report bugs and improvements on the current codebase. For such questions or issues, please use either the mailing lists or your dedicated support channel if you have a support contract with us. If so, you can directly Move this issue under the Support - Magnolia project. The reason we can't do it ourselves is so to avoid having to guess details about your setup. Your attention to detail will be appreciated. If this ends up being an actual bug in Magnolia (or something that can be improved), Cheers, -greg |