[MAGNOLIA-2615] Exporting on JBoss seems to be broken Created: 05/Feb/09 Updated: 23/Jan/13 Resolved: 24/Feb/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.0 |
| Fix Version/s: | 4.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Olivier Marti | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-284). |
||
| Attachments: |
|
||||||||
| 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 |
|
While installing a plain new instance, during the installation process (web gui guided) I receive an error with the extended templating kid: Magnolia Extended Templating Kit Module (version 1.0.0-rc1)
(see the attached error.log for stacktrace). I am able to login afterwards, but obv. the extended templating kid is not installed. Taking a look into the tmp xml-files while installing I see the following: <sv:node xmlns:mix="http://www.jcp.org/jcr/mix/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" So plenty of double-entries there, which is related to the error.log kindly the source of the error. |
| Comments |
| Comment by Philipp Bracher [ 05/Feb/09 ] |
|
This task uses a plain jcr export (to a temp file) and an import. So the main point is that the jcr export creates wrong files. |
| Comment by Philipp Bracher [ 05/Feb/09 ] |
|
A copy of a failing installation can be found here (for internal use only): /Volumes/Transfer/toPhilipp/jboss40test.tgz |
| Comment by Magnolia International [ 05/Feb/09 ] |
|
duplicate namespace declarations... can we get a look at the classpath? Multiple Xerces ? |
| Comment by Magnolia International [ 12/Feb/09 ] |
|
It doesn't seem to be related to any DataTransporter code like i suspected; even a straight call to jcrSession.exportSystemView(basepath, outputStream, false, false) exposes the same issue. |
| Comment by Magnolia International [ 12/Feb/09 ] |
|
Possibly related to https://issues.apache.org/jira/browse/JCR-1952 |
| Comment by Magnolia International [ 12/Feb/09 ] |
|
I was able to work around this by removing the xalan jar in JBOSS_HOME/lib/endorsed, with both JBoss 4.2.2 and 5.0.0 |
| Comment by Olivier Marti [ 13/Feb/09 ] |
|
I was able to confirm the workaround with success on Jboss 4.2.2, Jboss 4.0.5 is failing on startup with the missing xalan.jar. |
| Comment by Magnolia International [ 24/Feb/09 ] |
|
This is fixed by Jackrabbit 1.5.3 - see https://issues.apache.org/jira/browse/JCR-1952 No need to remove xalan anymore. |