Error in Weblogic Webservice

Question

I was using SAAJ 1.3 initially in WEBINF/lib and my code erred with
java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection
Error Location:
SOAPConnectionFactory factory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = factory.createConnection();
It erred on the above highlighted line. After some searching, I found that it could be because of Weblogic Server 9.2 not compatible with SAAJ 1.3. So I used SAAJ 1.2 and this error got solved. Now I am stuck up with the following error.
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPBody(SOAPMessageImpl.java:634)
Error Location:
SOAPElement attachmentElement = (SOAPElement)message.getSOAPBody().getElementsByTagNameNS(ws, "Attachment").item(0);
I am using SAAJ 1.2 but it says the class does not support SAAJ 1.1.
Again after some googling, I found that the error is due to some bug in Weblogic 9.2 when it is used with SAAJ 1.2. It was mentioned that following steps can be used to overcome this error.
1. Set classpath to latest saaj-impl.jar in startweblogic.cmd
2. Set the below 2 system properties in code.
System.setProperty("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
System.setProperty("javax.xml.soap.SOAPConnectionFactory","weblogic.wsee.saaj.SOAPConnectionFactoryImpl");
I tried this too but it didnt work.
How can i get rid of this error? Also if i m going to set the classpath to SAAJ 1.3 in startweblogic.cmd, will it not result in the first error i got i.e java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.
If my question is not very clear, please bear with me. I am pretty new to Webservice.
Can someone tell me how can i overcome this problem.

Answer 1

Have you included the IP addresses of the managed servers into the cluster address like for eg 192.127.1.2,192.127.1.2 in the cluster address field in the administration console? include it if not included that will fix the issue.
Regards,
Dinesh