» » » SOA 11g : Ws-Addressing Issues
Friday, April 29, 2011

In SOA Suite 11g, WS-Binding component includes WS-Addressing Headers in both request (when calling external web services) and response (when external clients call Composite web services).

This will result into errors as some service providers/clients doesn’t understand/process these headers and as a result  service invocation fails for both inbound and outbound.

To overcome this , you can configure the following property in composite.xml to suppress Ws-Addressing headers.

For Request

oracle.soa.ws.outbound.omitWSA = true

For Response

oracle.soa.addressing.response.enabled = false

These are not part of property list in JDeveloper. You need to add manually and it works.

Happy coding..

Posted by at Friday, April 29, 2011
Labels: ,

2 comments :

  1. Robert van MölkenMay 3, 2011 at 6:10 AM

    Still getting the tags in request message.

    I'm using following reference on 11.1.1.3:

    < reference name="GWS4All" ui:wsdlLocation="wsdl/gws-webintake-v0300.wsdl">
    < interface.wsdl interface="urn:gws-webintake#wsdl.interface(gwsPortType)"/>
    < binding.ws port="urn:gws-webintake#wsdl.endpoint(gwsService/gwsBindingPort)"
    location="wsdl/gws-webintake-v0300.wsdl" soapVersion="1.1">
    < property name="weblogic.wsee.wsat.transaction.flowOption" type="xs:string" many="false">WSDLDriven< /property>
    < property name="oracle.soa.ws.outbound.omitWSA" type="xs:boolean" many="false" override="may">true< /property>
    < /binding.ws>
    < /reference>

    What can be the problem here? Offcourse without the spaces.

    Thanks in advanced.

    ReplyDelete
  2. SatishMay 21, 2011 at 9:49 PM

    Robert, which tags are you referring here. Is it possible for you share the entire soap request for me to analyse ?

    ReplyDelete

Subscribe to: Post Comments ( Atom )