In Oracle SOA Suite 11g, the WS-Binding component includes the following
WS-Addressing headers:
– wsa:to
– wsa:replyTo
– wsa:action
Although the SOAP message generated by 11g is fully specification compliant, there are service provider implementations that do not understand these WS-Addressing headers when included in the
request message for synchronous operations. This is why the invocation fails.
To increase interoperability, the property oracle.soa.ws.outbound.omitWSA
has been introduced for the <binding.ws> element in the composite.xml file.
This property enables you to optionally suppress generation of WS-Addressing
headers in the request message when set to true. The default value is false.
Add following property under <binding.ws> tag in your composite.xml.
<binding.ws
-----
-----
<property name="oracle.soa.ws.outbound.omitWSA" type="xs:boolean"
many="false" override="may">true</property>
</binding.ws>
In SOA Suite 11g, the WS-Binding component includes the WS-Addressing
headers by default in the response messages.
But there are service consumer implementations that do not understand the WS-Addressing headers when
included in the response message in synchronous request-response scenarios. This is why the invocation fails.
To increase interoperability with clients (consumers) that do not support
WS-Addressing headers, a property named oracle.soa.addressing.response.enabled has been introduced.
This property enables you to optionally suppress generation of
WS-Addressing headers in the response message when set to true. The default
value is false.
Set the property in the composite.xml file as follows:
[snippet]
<binding.ws>
......<property name="oracle.soa.addressing.response.enabled" type="xs:boolean"
many="false" override="may">false</property>
</binding.ws>
[/snippet]
WS-Addressing headers:
– wsa:to
– wsa:replyTo
– wsa:action
Although the SOAP message generated by 11g is fully specification compliant, there are service provider implementations that do not understand these WS-Addressing headers when included in the
request message for synchronous operations. This is why the invocation fails.
To increase interoperability, the property oracle.soa.ws.outbound.omitWSA
has been introduced for the <binding.ws> element in the composite.xml file.
This property enables you to optionally suppress generation of WS-Addressing
headers in the request message when set to true. The default value is false.
Add following property under <binding.ws> tag in your composite.xml.
<binding.ws
-----
-----
<property name="oracle.soa.ws.outbound.omitWSA" type="xs:boolean"
many="false" override="may">true</property>
</binding.ws>
In SOA Suite 11g, the WS-Binding component includes the WS-Addressing
headers by default in the response messages.
But there are service consumer implementations that do not understand the WS-Addressing headers when
included in the response message in synchronous request-response scenarios. This is why the invocation fails.
To increase interoperability with clients (consumers) that do not support
WS-Addressing headers, a property named oracle.soa.addressing.response.enabled has been introduced.
This property enables you to optionally suppress generation of
WS-Addressing headers in the response message when set to true. The default
value is false.
Set the property in the composite.xml file as follows:
[snippet]
<binding.ws>
......<property name="oracle.soa.addressing.response.enabled" type="xs:boolean"
many="false" override="may">false</property>
</binding.ws>
[/snippet]
0 comments:
Post a Comment