type=xs:string/
/xs:sequence
/xs:complexType
--
View this message in context:
http://www.nabble.com/Generated-wsdl-in-XFire-Versus-CXF-tf4338370.html#a13131774
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
You can use the simple front end[1] instead of jaxws front end[2].
[1]http://cwiki.apache.org/CXF20DOC/simple-frontend.html
[2]http://cwiki.apache.org/CXF20DOC/jax-ws.html
Willem.
William Leung wrote:
I am trying setup a client in vs.net.
So sad, that vs.net only reconized the XFire
this message in context:
http://www.nabble.com/Generated-wsdl-in-XFire-Versus-CXF-tf4338370.html#a13132953
Sent from the cxf-user mailing list archive at Nabble.com.
We had to change the format of the generated WSDL to meet the
requirements of the various TCK's.
I think the major differences are:
1) The part names in the messages
2) The nillable and minOccurs=0 things in the elements in the wrappers
3) Using a names complexType instead of an
-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 4:16 PM
To: cxf-user@incubator.apache.org
Cc: William Leung
Subject: Re: Generated wsdl in XFire Versus CXF
We had to change the format of the generated WSDL to meet the
requirements of the various TCK's.
I
Hi all,
I notice that in CXF, the xsd elements for method names have a type
attribute. This was not the case in XFire.
Here is an example of what I am talking about. My question is, is there a
way to get CXF to spit out wsdl exactly as XFire?
Thanks,
Jacob
XFire
==
xsd:element
