Return-Path: Delivered-To: apmail-incubator-cxf-user-archive@locus.apache.org Received: (qmail 51923 invoked from network); 10 Oct 2007 12:21:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2007 12:21:41 -0000 Received: (qmail 61832 invoked by uid 500); 10 Oct 2007 12:21:28 -0000 Delivered-To: apmail-incubator-cxf-user-archive@incubator.apache.org Received: (qmail 61651 invoked by uid 500); 10 Oct 2007 12:21:27 -0000 Mailing-List: contact cxf-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-user@incubator.apache.org Delivered-To: mailing list cxf-user@incubator.apache.org Received: (qmail 61641 invoked by uid 99); 10 Oct 2007 12:21:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 05:21:27 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of bim2007@basistech.com does not designate 199.88.205.99 as permitted sender) Received: from [199.88.205.99] (HELO mail.basistech.com) (199.88.205.99) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 12:21:29 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: WSDL not recognized by vs net Date: Wed, 10 Oct 2007 08:21:07 -0400 Message-ID: In-Reply-To: <13133442.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WSDL not recognized by vs net Thread-Index: AcgLKycxzt54f0lfRPOKefW+JDlmnwADMVVw References: <13132033.post@talk.nabble.com> <470CA9B0.8080108@iona.com> <13133442.post@talk.nabble.com> From: "Benson Margulies" To: X-Virus-Checked: Checked by ClamAV on apache.org 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 >=20 >=20 > Sorry for the "newbie" question. >=20 > Is vs only support not wrapped? >=20 >=20 >=20 > 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 > >> > >> > >> > >> > >> > >> > >> > >> > >> to > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> 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 > >> > > > > >=20 > -- > 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.