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 schema format but not the CXF one. >From the hello world example, the VS.net reconized the operation as: CXF ========================= "HelloWorld" Description Methods sayHi ( sayHi As sayHi ) As sayHiResponse while XFire format is well XFire ========================= "HelloWorld" Description Methods sayHi ( sayHi As string ) As string So can I have an option that to use the XFire format, I preferred java first only. jacobmarcus20 wrote: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 name="getAsset"> <xsd:complexType> <xsd:sequence> <xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string"/> </xsd:sequence> </xsd:complexType> </xsd:element> CXF ==== <xs:element name="getAsset" type="tns:getAsset"/> <xs:complexType name="getAsset"> <xs:sequence> <xs:element minOccurs="0" name="arg0" type="xs:string"/> </xs:sequence> </xs:complexType>
