[ 
https://issues.apache.org/jira/browse/AXIS2-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670922#action_12670922
 ] 

Roy A. Wood Jr. commented on AXIS2-4228:
----------------------------------------

Hi Andreas,

I mostly use Maven to run the tests and I did notice that the pom file 
specifies where the factory implementations are. However, with the change that 
was introduced in
rev. 733910, we (IBM JDK users) started getting the following test errors in 
saaj tests:

Caused by: java.lang.NoClassDefFoundError: 
com/sun/xml/messaging/saaj/soap/SOAPDocumentImpl
        at 
com.sun.xml.messaging.saaj.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:119)
        at 
com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:109)
        at 
com.sun.xml.messaging.saaj.soap.MessageImpl.init(MessageImpl.java:400)
        ... 30 more

CAUSE:

java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/SOAPDocumentImpl
        at 
com.sun.xml.messaging.saaj.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:119)
        at 
com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:109)
        at 
com.sun.xml.messaging.saaj.soap.MessageImpl.init(MessageImpl.java:400)
        at 
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:309)
        at 
com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.createMessage(SOAPMessageFactory1_1Impl.java:93)
        at 
org.apache.axis2.saaj.SOAPEnvelopeTest.testDetachBody(SOAPEnvelopeTest.java:114)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)

-----------------------------------------------

This may somehow be a problem with processing the pom file when using IBM's 
JDK. This does get us past the test problems, 
but you're correct that we should probably not be using two different 
implementations. I'll look at this some more and am open to suggestions as well.

> 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.

Reply via email to