This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin in Action and have Dmitry Jemerov & Svetlana Isakova on-line!
See this thread for details.
Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Does WSAD 5.1.0 support SOAP 1.2  RSS feed

Anup Bansal
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am developing a WebService Client .The webservice we are accessing requires that we use SOAP 1.2 for all communications.

WSAD version: 5.1.0
Local Server: Integration Test Environment 5.1
Comiler version = 1.4

For the purpose to satisfy the requirements, I am using the SAAJ 1.3 APIs. I have imported saaj-api.jar and saaj-impl.jar. I am using WSAD 5.1.0 as the IDE.

I am unable to create a SOAP message. The same works when I use the default SAAJ APIs available with WSAD.

//Create Message
MessageFactory requestMessageFactory = MessageFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL);
SOAPMessage requestMessage = requestMessageFactory.createMessage();

//Get the SOAPBody
SOAPEnvelope requestEnvelope = requestMessage.getSOAPPart().getEnvelope();
requestBody = requestEnvelope.getBody().addBodyElement(requestEnvelope.createName("Request");

//Add Body element to SOAP Body
SOAPElement hdrTag = requestBody.addChildElement(requestEnvelope.createName("Hdr"));
SOAPElement reqBdyTag = requestBody.addChildElement(requestEnvelope.createName("ReqBdy"));


The above line returns the value as [Request: null]

The same code when run using the default jars present in WSAD webservices.jar (conforming to SOAP 1.1), the following is returned:
<soapenv:Envelope xmlns:soapenv="" xmlns:soapenc="" xmlns:xsd="" xmlns:xsi=""><soapenv:Body><Request xmlns=""> <Hdr xmlns=""> hdr</Hdr><ReqBdy xmlns="">reqbdy</ReqBdy></soapenv:Body></soapenv:Envelope>

In the debug mode, when i check the value of the variable requestBody it shows all the fields properly populated.

1. Can you please let me know where I may be going wrong?
2. Is this a problem due to compatibility issue?
3. Is this a problem with the implementation jar of SAAJ 1.3?
3. Have I forgotten to include some importatn jars?
4. If SAAJ 1.3 is not preferable for implementation of SOAP 1.2 in WSAD, what other ways I can generate/handle SOAP request/response?
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!