You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/11/10 11:20:17 UTC

[jira] [Commented] (CAMEL-6922) XmlConverter cannot convert from ElementNSImpl to Document

    [ https://issues.apache.org/jira/browse/CAMEL-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818413#comment-13818413 ] 

Claus Ibsen commented on CAMEL-6922:
------------------------------------

What JDK are you using?

The Oracle JDK on osx, the ElementNSImpl class only implements Node (does NOT implement NodeList)

> XmlConverter cannot convert from ElementNSImpl to Document
> ----------------------------------------------------------
>
>                 Key: CAMEL-6922
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6922
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.11.2
>         Environment: HP-UX, JDK 6.14, 7.06
>            Reporter: Arseniy Tashoyan
>            Priority: Minor
>              Labels: converter, dom, xml
>
> XmlConvertor cannot convert from org.apache.xerces.dom.ElementNSImpl to org.w3c.dom.Document. Class ElementNSImpl implements both interfaces org.w3c.dom.Node and org.w3c.dom.NodeList. While type converter lookup iterates from ElementNSImpl through it's superclasses and implemented interfaces, it reaches NodeList first. Therefore the
> {color:green}
> Node toDOMNodeFromSingleNodeList(NodeList)
> {color}
> method is selected for conversion. However this method returns null for any NodeList with more than one node. This leads to null in a message's body.
> This issue is not detected on Linux, because on Oracle JDK lookup reaches Node before NodeList and the
> {color:green}
> Document toDOMDocument(Node)
> {color}
> method is selected for conversion.



--
This message was sent by Atlassian JIRA
(v6.1#6144)