You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Henry Zongaro (JIRA)" <xa...@xml.apache.org> on 2006/03/14 22:15:39 UTC
[jira] Resolved: (XALANJ-2273) Namespace problem when serializing
from JAXB 2.0
[ http://issues.apache.org/jira/browse/XALANJ-2273?page=all ]
Henry Zongaro resolved XALANJ-2273:
-----------------------------------
Resolution: Invalid
I see that the JAXB issue [1] has been closed as invalid, with the reason that JAXB requires only namespace-aware DOMs. I am assuming, based on that piece of information, that the Xalan-J processor is receiving invalid input. If you disagree, please feel free to reopen the bug report.
[1] https://jaxb.dev.java.net/issues/show_bug.cgi?id=123
> 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: 2.7, Latest Development Code
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org