cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies" <bim2...@basistech.com>
Subject RE: WSDL not recognized by vs net
Date Wed, 10 Oct 2007 12:21:07 GMT
In my experience, the VS2005 wsdl.exe doesn't like bare, at least when
CXF 2.0.2 and Aegis+JAX-WS are at work. It complains bitterly of name
conflicts.

If this is supposed to work, I'll concoct a JIRA.

> -----Original Message-----
> From: William Leung [mailto:lwr@21cn.com]
> Sent: Wednesday, October 10, 2007 6:48 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: WSDL not recognized by vs net
> 
> 
> Sorry for the "newbie" question.
> 
> Is vs only support not wrapped?
> 
> 
> 
> Willem2 wrote:
> >
> > The WSDL that you got from from CXF is Document/Literal Wrapped.
> > If you want to set it to  the Document/Literal model , you need to
set
> > the JaxWsServiceFactory's wrapped attribute to be false.
> >
> > Willem.
> >
> > William Leung wrote:
> >> I am testing CXF and sadlly found that our method parameters and
> returns
> >> are
> >> not recognized in vs net.
> >>
> >> VS NET recongnized the sayHi function as
> >> --- sayHi ( sayHi As sayHi ) As sayHiResponse
> >> it should be
> >> --- sayHi ( arg0 As string) as string
> >>
> >>
> >> When I change the wsdl manually from
> >>
> >>       <xsd:element name="sayHi" type="tns:sayHi"/>
> >>       <xsd:complexType name="sayHi">
> >>         <xsd:sequence>
> >>           <xsd:element minOccurs="0" name="arg0"
type="xsd:string"/>
> >>         </xsd:sequence>
> >>       </xsd:complexType>
> >>
> >> to
> >>
> >>       <xsd:element>
> >>         <xsd:complexType>
> >>           <xsd:sequence>
> >>             <xsd:element minOccurs="0" name="arg0"
type="xsd:string"/>
> >>           </xsd:sequence>
> >>         </xsd:complexType>
> >>       </xsd:element>
> >>
> >> It worked, but I have no idea how could I make this changes without
> >> switch
> >> to "wsdl first" (I dont want to, I have just too many methods to
export)
> >>
> >> Any help will be very appreciated
> >>
> >
> >
> 
> --
> View this message in context:
http://www.nabble.com/WSDL-not-recognized-
> by-vs-net-tf4599448.html#a13133442
> Sent from the cxf-user mailing list archive at Nabble.com.


Mime
View raw message