cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies" <bim2...@basistech.com>
Subject RE: WSDL and parts
Date Mon, 30 Jul 2007 18:56:50 GMT
Hmm. CXF aegis definitely uses "parameters" for doc/literal with no
special requests for mapping for the inputs, but wraps the outputs in a
part named 'results'.

Perhaps more to the point, the goal of this code is to find the
descriptions of the parameters and the result.

> -----Original Message-----
> From: Balaji Ravi [mailto:balajimravi@gmail.com]
> Sent: Monday, July 30, 2007 2:53 PM
> To: cxf-dev@incubator.apache.org
> Subject: Re: WSDL and parts
> 
> Hi,
> 
> You cannot depend on "parameters" word. .NET uses this to mark its
wsdl as
> a
> wrapped doc-literal but it definitely shouldn't be considered a
standard
> way.
> 
> Only a wrapped doc-literal wsdl would have input & output messages
with
> one
> part not the doc-literal wsdl.
> 
> - Balaji
> 
> On 7/30/07, Benson Margulies <bim2007@basistech.com> wrote:
> >
> > I'm working on the wsdl2js code as it interacts with CXF.
> >
> > The code, written to work with doc/literal services, thinks that it
can
> > do this from an operation:
> >
> > op.getOutput().getMessage().getPart("parameters")
> >
> > Such is not the case with Aegis. The reason for this belief is that
the
> > other kit we've used here to make WSDL files names the part
'parameters'
> > even for the output.
> >
> > CXF calls the input 'parameters' and the output 'result'.
> >
> > The question is, can the message have more than one part other than
> > 'fault'?
> >

Mime
View raw message