[
https://issues.apache.org/jira/browse/AXIS2-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670927#action_12670927
]
Andreas Veithen commented on AXIS2-4228:
----------------------------------------
SOAPDocumentImpl is part of saaj-impl, but it extends DocumentImpl from Sun's
internal copy of Xerces! This should explain the problem you see on IBM's JDK.
I will have a look at the available versions of saaj-impl to see if there is
one that doesn't have this problem.
Other question: is SAAJ part of the IBM JDK version 1.5?
> SAAJ test cases no longer work with IBM's SDK
> ---------------------------------------------
>
> Key: AXIS2-4228
> URL: https://issues.apache.org/jira/browse/AXIS2-4228
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: saaj
> Reporter: Roy A. Wood Jr.
> Assignee: Roy A. Wood Jr.
>
> In rev. 733910, the introduction of the custom test runners broke the tests
> when the tests are built with IBM's JDK.
> The paths to the following factories are different for IBM:
> System.setProperty("javax.xml.soap.MessageFactory",
>
> "com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
> System.setProperty("javax.xml.soap.SOAPFactory",
>
> "com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl");
> System.setProperty("javax.xml.soap.SOAPConnectionFactory",
>
> "com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory");
> System.setProperty("javax.xml.soap.MetaFactory",
> "com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl");
> The simple fix is to properly set these system properties when using IBM's
> JDK.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
