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 anonymousType in the wrapper element. Is there any way you could "play" with the CXF wsdl to see which of the above is causing the .NET issue? (My gut feeling says #3, I would start with that.) I don't have a Windows box so it's not something I can try. If you can figure out which it is, we can probably add a configuration setting to make it output the way that is needed. Dan On Wednesday 10 October 2007, 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> -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
