Making addressing headers optional with composite applications

View: New views
1 Messages — Rating Filter:   Alert me  

Making addressing headers optional with composite applications

by SourabhPawar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello,

 

I am trying to implement support for addressing headers with a composite application.

 

By adding the following policy to the CA WSDL, it is possible to add support for addressing headers to the service.

 

    <wsp:Policy wsu:Id="casaBinding4Policy">

        <wsp:ExactlyOne>

            <wsp:All>

                <wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/>

            </wsp:All>

        </wsp:ExactlyOne>

    </wsp:Policy>

 

However, when this is done, addressing headers become required. We would want to have the addressing headers as optional, and return relevant addressing headers in the response if the request had any.

 

When looking for solutions, we tried adding a ‘required=”false”’ to the UsingAddressing –

           

<wsaws:UsingAddressing required="false" xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/>

 

This did not help either.

 

How can we achieve having these optional addressing headers?

 

Thanks in advance,
Sourabh