I understand your case now: 1) You have a componentType reference interface contract which is the doc-literal WSDL. 2) You configure the reference binding interface contract to be doc-literal-wrapper WSDL.
What databinding do you configure for 1 and 2? What payload do you have for the request when the source component makes the outbound call on the reference? An Object[] of "xml" elements? The databinding framework will detect 1 is not wrapped while 2 is wrapped. It first tries to find if there is a wrapper for 1 to contain all the parts. If not, it will try to convert all the parts one by one and add them into the wrapper object for 2. Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Jan 6, 2011, at 11:59 AM, Jean-Sebastien Delfino wrote: > 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
