Mailing-List: contact cxf-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Wsdl2Java Generating BARE not WRAPPED
Date: Thu, 29 Mar 2007 15:26:11 -0400
Message-ID: <D1AE8A943CFBEE408A89F87397B024D401131066@tewk-mbpf2>
In-Reply-To: <7b774c950703291141m356e5aecu961fbccac0af3d55@mail.gmail.com>
Thread-Topic: Wsdl2Java Generating BARE not WRAPPED
Thread-Index: AcdyMfrc/Q4GMESuRim6n1EtRNiyRAABgmtQ
From: "Christopher Moesel" <Christopher_Moesel@avid.com>
To: <cxf-user@incubator.apache.org>

Thanks Dan-- I appreciate the help!

-Chris

-----Original Message-----
From: Dan Diephouse [mailto:dan@envoisolutions.com]=20
Sent: Thursday, March 29, 2007 2:42 PM
To: cxf-user@incubator.apache.org
Subject: Re: Wsdl2Java Generating BARE not WRAPPED

Thanks for the bug report. We'll try to fix this soon!
- Dan

On 3/29/07, Christopher Moesel <Christopher_Moesel@avid.com> wrote:
>
> After some investigation (commenting out and uncommenting out sections
> of WSDL)-- I've determined the cause of the problem.
>
> If a doc/literal wrapped WSDL uses xsd:any in the wrapped request or
> response type, then the WSDL2Java tool will generate the interface
with
> style SOAPBinding.ParameterStyle.BARE.
>
> I don't believe this is the intended behavior (is it?) and have
> submitted a bug report (with example code/wsdl):
> https://issues.apache.org/jira/browse/CXF-502
>
> At this point, this is a stopper for me porting my service from XFire
to
> CXF.  Once the bug is resolved, I'll give it another shot.
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: James Mao [mailto:james.mao@iona.com]
> Sent: Thursday, March 29, 2007 10:05 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: Wsdl2Java Generating BARE not WRAPPED
>
> Hi Chris,
>
> I suggest you open the validate option, to check if there is any
> errors/warnings during processing.
> And also you can try the JAXWS RI, and see if generated as you
expected.
> The last option, also the quickest option is fire an issue on [1] ,
> attach your wsdl.
>
> [1] https://issues.apache.org/jira/browse/CXF
>
> Thanks,
> James.
> > I'm using the Maven 2 plugin for executing Wsdl2Java.  Although my
> WSDL
> > is in doc/literal wrapped style, the generated code specifies
> > SOAPBinding.ParameterStyle.BARE.  And the style of the generated
> methods
> > is also bare-for example:
> >
> >
> >
> >     @SOAPBinding(parameterStyle =3D SOAPBinding.ParameterStyle.BARE)
> >
> >     @WebResult(targetNamespace =3D "http://mycompany.com/ws", =
partName
=3D
> > "body", name =3D "MyOperationResponse")
> >
> >     @WebMethod(operationName =3D "MyOperation")
> >
> >     public com.mycompany.ws.MyOperationResponseType myOperation(
> >
> >         @WebParam(targetNamespace =3D "http://mycompany.com/ws",
> partName
> > =3D "body", name =3D "MyOperation")
> >
> >         com.mycompany.ws.MyOperationType body
> >
> >     );
> >
> >
> >
> > If I run the same WSDL through the XFire 1.2.5 generator, it
correctly
> > identifies it as doc/literal wrapped and generates code in that
style.
> > So I suspect my WSDL is correct.
> >
> >
> >
> > I didn't see any open issues regarding this-is anyone else having
> > problems with it?  Any suggestions for things I might try?  Any
> gotchas
> > between how XFire identifies wrapped style and how CXF identifies
it?
> >
> >
> >
> > Thanks,
> >
> > Chris
> >
> >
> >
> >
> >
> >
> >
>
>


--=20
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog