On 01/06/2011 09:32 AM, Raymond Feng wrote:
The first WSDL is document-literal style, but it is not WS-I compliant as it 
has more than more child elements (two parts) for the soap:Body. You will 
end-up with the following message (please note the operation is not in the 
message at all).
<soap:envelope>
     <soap:body>
         <symbol>IBM</symbol>
         <time>5.0</time>
     </soap:body>
</soap:envelope>
The second WSDL is document-literal-wrapper style. You will have a request 
message like:

<soap:envelope>
     <soap:body>
        <getQuote>
                <symbol>IBM</symbol>
                <time>5.0</time>
        </getQuote>
     </soap:body>
</soap:envelope>
Do you have the 1st WSDL for the service side and 2nd WSDL for the reference 
side?

I create the first WSDL (non-wrapped) by introspecting my component implementation. It is used as the 'interface contract' of my component reference.

The second WSDL (wrapped) is used to configure the binding of the reference. It is used as the 'binding interface contract' of that binding.

That binding is my own binding extension (not the WS binding).

The target service is remote over a network and using the second WSDL as well, but (see below) my question is not about that segment of the communication, it is about what happens between the component and the reference binding.

Do you use generated Java interfaces from WSDL?

No.

Are both sides using Tuscany?

Yes.

I'm not sure if we support the 1st style in Tuscany binding.ws.
If the invocation is over SOAP/HTTP (not local remotable invocation), we hand 
the data transformation at both ends.
Basically, the conversion is between the componentType interfaces and binding 
interface contracts.

My question is what happens in the invocation chain between the ImplementationProvider holding my component reference (not-wrapped) and the ReferenceBindingProvider of the binding configured on that component reference (wrapped).

Can I rely on the DataBinding mediation capability to transform the data presented by the component ImplementationProvider (not wrapped) to the format expected by the ReferenceBindingProvider?

Thanks
--
Jean-Sebastien

Reply via email to