[
http://issues.apache.org/jira/browse/XALANJ-2273?page=comments#action_12367630
]
Golgoth 14 commented on XALANJ-2273:
------------------------------------
Here the results with different jvm argument
"-Djavax.xml.transform.TransformerFactory" :
(
I've modified the build2.xml file like:
<jvmarg
line="-Djavax.xml.transform.TransformerFactory=org.apache.xalan.xsltc.trax.TransformerFactoryImpl"/>
under the java task.
)
1) with
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
The both outputs (with an without namespace aware) are correct.
2) with
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
The outputs are different.
3) with
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.xsltc.trax.TransformerFactoryImpl
The both outputs (with an without namespace aware) are correct.
It seems the both XSLTC versions of the factory output a non "polluted" XML.
There are three different version of the XALAN processor ?
> Namespace problem when serializing from JAXB 2.0
> ------------------------------------------------
>
> Key: XALANJ-2273
> URL: http://issues.apache.org/jira/browse/XALANJ-2273
> Project: XalanJ2
> Type: Bug
> Components: Xalan, Serialization
> Versions: Latest Development Code, 2.7
> Environment: Windows XP Pro
> java version "1.5.0_06"
> JAXB 2.0 EA3
> Xerces 2.7.1
> Xalan 2.7.0 and trunk
> Reporter: Golgoth 14
> Priority: Minor
> Attachments: jaxb-test.zip
>
> The marshalling of a JAXB object created by the parsing of XML data with the
> Xerces parser
> gives two differents results if the classpath contains only xerces.jar or if
> it contains xerces.jar, xalan.jar and serializer.jar.
> 1) Classpath with xerces only :
> [java] <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> [java] <dataDetail xmlns="http://my.namespace.com/a";
> name="datadetail-001">
> [java] <data id="data-001">
> [java] <n:test xmlns:n="http://my.namespace.com/n";>data</n:test>
> [java] </data>
> [java] <data id="data-002">
> [java] <n:test xmlns:n="http://my.namespace.com/n";>data</n:test>
> [java] </data>
> [java] </dataDetail>
> 2) Classpath with xerces, xalan and serializer :
> [java] <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> [java] <dataDetail xmlns="http://my.namespace.com/a";
> name="datadetail-001">
> [java] <data id="data-001">
> [java] <n:test xmlns:n="http://my.namespace.com/n";>data</n:test>
> [java] </data>
> [java] <data id="data-002">
> [java] <test xmlns:ns2="http://my.namespace.com/a"; xmlns=""
> xmlns:n="http://my.namespace.com/n";>data</test>
> [java] </data>
> [java] </dataDetail>
> I've make test with the released and with the trunk versions of Xalan.
> First, I had posted this bug on the JAXB issue tracker but the JAXB team
> investigations indicated that the problem came from Xalan.
> I've a full test case that you could run with ANT. I will try to attach it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
