Apache OpenOffice (AOO) Bugzilla – Issue 35009
XSLT filter shall run with Java 5
Last modified: 2005-06-30 12:49:53 UTC
The XSLT filter, part of the optional 'sample XSLT filter' setup component, have to be adapted to run with Java 5.
Correct SO7 PP4 flag?
JS: Target is 1.1.4; 1.1.3 has been just released :-)
Status XSLT filter using Java 5: -Docbook import & export smoke test passed -SpreadsheetML import passed -XHTML import (Exception during compiling stylesheet) Fix: To change as little as possible to the environment of the office, mapped the current state of XHTML filter into the exisiting file structure Test: No further exception, but massive data loss due to XSLTC issue (works fine with Xalan). Issue triggered by calling a template within a variable. Added multiple workarounds for this issue, but in case of recursion we are quite lost (e.g. tables). Nearly no table output with XSLTC Tried to address XALAN, but no second XSLT processor in Java, they removed XALAN. Possible solutions: Massive work impact on workaround or wait for Java 5 patch or shipping with Xalan. Works fine with Xalan2.0 even under Java5, but not with the build in XSLTC processor. -WordML import (Exception during compiling stylesheet) Fix: To change as little as possible to the environment of the office, mapped the current state of Wordml import filter into the exisiting file structure. Fixing namespace problems, which even blocked Xalan 2.0. Nevertheless without effect. Works fine with Xalan2.0 even under Java5, but not with the build in XSLTC processor. Possible solutions: Massive work impact on workaround or wait for Java 5 patch or shipping with Xalan. Fixes of this task has been checked in, further progress have to be coordinated with management and should be addressed as follow up tasks.
reopen, obviously I have to move it first to QA and change status afterwards...
To QA
Fixed
Tested under WindowsXP
Wrote an Java 5 issue concerning the wordml filter: Synopsis: Compilation of StarOffice wordml XSLT filter via XSLTC throws exception http://bt2ws.central.sun.com/CrPrint?id=6175602 Furthermore, wrote the developer directly, by some chance I might get information for a workaround for the wordml stylesheet tomorrow.
Too many problems around. I don't think that this solution is okay for a PP.
Re-Assigning to sus.
In the release meeting it will be discussed if XALAN 2.0 will be bundled with the Office. Aside of adding the JARS, we should change the java.ini, not only by mentioning these new JARS, but loading them before the usual Java path. This would have certainly no advantage against Java 5, where it would be sufficient to add these to the class path as no othe XALAN has been integrated, but the internal Java 1.4 version of Xalan would be outmanoevered only by the adding the following line to java.ini: -Xbootclasspath/p:<xalan-jars-path> Many issues have been fixed in Xalan 2.0 so the filter output will be a lot better than before.
Due to pressure of time, it was decided to shift this task to OOo 1.1.5. In OOo1.1.4 we have to live with the restriction and Java 5. To work around this problem OOo 1.1.4 should use still Java 1.4.2.
This task is blocked / depends on a task of Martin Hollmichel to clarify the possible integration of Xalan into SO7.
In need of the integration of Xalan to fix this issue.
- Added Xalan module to srx645 - Added dependency in filter module to Xalan module - Added Xalan jars to manifest of XSLTFilter.jar (will be used and loaded by XSLT filter only) - Added Xalan jars to scp-so - wrote mail to RE (release engineer) for adding module to SRX645
Classloading does not work as in SO8. Java.ini / javarc have to be adapted for classpath. Depending task added.
Will work after 38324 is fixed -> set to fixed
reopen and self transfer because of xalan memory leak re-open issue and reassign to lo@openoffice.org
reassign to lo@openoffice.org
reset resolution to FIXED
implemented and tested caching machanism for transformations in XSLTransformer.java, reassigning to svante re-open issue and reassign to sus@openoffice.org
reassign to sus@openoffice.org
Ready for QA re-open issue and reassign to jsi@openoffice.org
reassign to jsi@openoffice.org
Tested and error free is the DocBook Load/Save test with Java 5. (Update 03) and Java 1.4.2.
Works fine on all platforms with _03.