Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 90841 invoked by uid 500); 13 Aug 2002 15:08:23 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 90827 invoked from network); 13 Aug 2002 15:08:22 -0000 Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Aug 2002 11:05:12 -0400 Message-ID: From: "Riggs, David" To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I ripped the "elementFormDefault=3D'qualified'" out of the WSDL and WSDL2Java put the following into my client-side bean code: field.setXmlName(new javax.xml.namespace.QName("", "MissionName")); It very happily accepts the SOAP response from MSSTK3 now... Is this WSDL incorrectly specifying that the elements are qualified when they are really unqualified? David A. Riggs Science Applications International Corporation - SAIC (304)284-9000x201 driggs@asset.com > -----Original Message----- > From: Scott Nichol [mailto:snicholnews@scottnichol.com]=20 > Sent: Tuesday, August 13, 2002 10:45 AM > To: axis-dev@xml.apache.org > Subject: Re: Axis Chokes on Complex Types from MS Soap 3.0 >=20 >=20 > >>>> > I have not tried a .NET client, only Axis (which works if > I manually remove the namespace from the generated code) > <<<< >=20 > From what Glen said, it should also work if you manually=20 > remove elementFormDefault=3D'qualified' from the WSDL, right? >=20 > Scott >=20