You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Benson Margulies <bi...@basistech.com> on 2007/07/30 20:37:16 UTC
WSDL and parts
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'?
RE: WSDL and parts
Posted by Benson Margulies <bi...@basistech.com>.
OK, this will call forth some additional cross-checking as we clean up
this code.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Tuesday, July 31, 2007 12:35 PM
> To: cxf-dev@incubator.apache.org
> Cc: Benson Margulies
> Subject: Re: WSDL and parts
>
>
> Benson,
>
> On Monday 30 July 2007 14:37, Benson Margulies 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'.
>
> I think naming it "result" had something to do with issues trying to
get
> the JWS TCK to pass. I don't remember the details (and I probably
> wouldn't be able to say anyway).
>
> > The question is, can the message have more than one part other than
> > 'fault'?
>
> Well, yes. If the wrapped/doc/lit has headers, the message may have
> more than one part. However, only one part would be mentioned in
> the "soap:body" section of the binding. All the other parts would be
> have soap:header descriptions.
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
Re: WSDL and parts
Posted by Daniel Kulp <dk...@apache.org>.
Benson,
On Monday 30 July 2007 14:37, Benson Margulies 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'.
I think naming it "result" had something to do with issues trying to get
the JWS TCK to pass. I don't remember the details (and I probably
wouldn't be able to say anyway).
> The question is, can the message have more than one part other than
> 'fault'?
Well, yes. If the wrapped/doc/lit has headers, the message may have
more than one part. However, only one part would be mentioned in
the "soap:body" section of the binding. All the other parts would be
have soap:header descriptions.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
RE: WSDL and parts
Posted by Benson Margulies <bi...@basistech.com>.
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 <bi...@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'?
> >
Re: WSDL and parts
Posted by Balaji Ravi <ba...@gmail.com>.
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 <bi...@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'?
>