[MAGNOLIA-2468] Problem installing Magnolia: Premature end of file due missing xalan jar Created: 06/Nov/08 Updated: 28/Feb/14 Resolved: 28/Feb/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.6.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Thomas Anderson | Assignee: | Magnolia International |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.2 Linux / Tomcat 5.5.23 / Java jdk1.6.0_06 / magnolia-empty-webapp.war |
||
| Issue Links: |
|
||||||||
| 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 |
|
INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(load:121) 06.11.2008 10:00:18 Initializing content repositories |
| Comments |
| Comment by Magnolia International [ 06/Nov/08 ] |
|
Hi, One of your workspace.xml files seem to be corrupted. Please use either the mailing lists or your dedicated support channel if you have a support contract with us for such questions. This Jira project is used to report bugs and improvements on the current codebase. If this ends up being an actual bug in Magnolia (or something that can be improved), we'll be happy to reopen this issue (or create a new one) with the relevant details to fix it ! Cheers, -greg |
| Comment by Philipp Bracher [ 14/Nov/08 ] |
|
In case you run into that issue you have to do the following:
|
| Comment by Magnolia International [ 20/May/09 ] |
|
Actually, I'd like to reopen this; at the very least, our WorkspaceXmlUtil should be a little more lenient. If a workspace.xml file is corrupt, it should report or ignore it instead of completely stopping the startup (i.e interrupting the install - this is only use on install of core so far). How does Jackrabbit behave with such a file, when actually starting the repository ? |