You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Robert Varga (JIRA)" <ji...@apache.org> on 2016/05/25 12:38:12 UTC

[jira] [Created] (KARAF-4539) Do not default to Xalan as the TransformerFactory implementation

Robert Varga created KARAF-4539:
-----------------------------------

             Summary: Do not default to Xalan as the TransformerFactory implementation
                 Key: KARAF-4539
                 URL: https://issues.apache.org/jira/browse/KARAF-4539
             Project: Karaf
          Issue Type: Bug
    Affects Versions: 3.0.6, 3.0.5
            Reporter: Robert Varga


The switch to Xalan-J as the default transformer factory in KARAF-3956 has broken OpenDaylight XML processing code in multiple places.

The first issue is that Xalan's TransformerImpl does not support StAXResult, which is a regression from JVM defaults and requires clear hacks to workaround: https://github.com/opendaylight/yangtools/commit/dd5487e20c8a9b2191516b230ccd4e16896652dd.

The other issue seems to be correctness of transformation from DOM to SAX. The effect is that code in https://github.com/opendaylight/netconf/blob/3062d9b5a6704075b4b10a8e1ad481738ca370c7/netconf/netconf-netty-util/src/main/java/org/opendaylight/netconf/nettyutil/handler/NetconfEXIToMessageDecoder.java fails to emit proper namespaces. This looks related to https://issues.apache.org/jira/browse/XALANJ-2382 and/or https://bugs.openjdk.java.net/browse/JDK-6305029.

In both cases code which runs just fine with multiple JVMs and worked with karaf-3.0.3 fails with 3.0.6 unless non-trivial surgery is performed: https://git.opendaylight.org/gerrit/39368.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)