axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Nichol <snicholn...@scottnichol.com>
Subject Re: Axis Chokes on Complex Types from MS Soap 3.0
Date Tue, 13 Aug 2002 16:26:16 GMT
The only part of the schema that is overridden is the
elementFormDefault='qualified' attribute.  To me, that just seems like part
of the evolution of two specs.  It would be nice if future versions of the
specs would specifically address this.  I would prefer the WSDL spec to
specify that encoded bodies cannot use types from schema that have
elementFormDefault='qualified', so that the situation becomes a constraint
rather than a place where one spec "overrides" the other.

Scott Nichol

----- Original Message -----
From: "Labib Iskander, Marcus" <ml@cm4all.com>
To: <axis-dev@xml.apache.org>
Sent: Tuesday, August 13, 2002 12:07 PM
Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0


Hi,
where is the sense in specifying a schema as part of a wsdl when it is not
used, because soap encoding is used later on in the soap binding.
Could you please tell me where exactly you found the cited paragraph in the
spec. After some further thought I might ask the WG.

Marcus

> -----Original Message-----
> From: Glen Daniels [mailto:gdaniels@macromedia.com]
> Sent: Tuesday, August 13, 2002 5:11 PM
> To: 'axis-dev@xml.apache.org'
> Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0
>
>
>
> No, the WSDL (schema really) means what it says, it's just
> that that apparently gets overriden by the fact that the
> message is SOAP encoded.  I've just fixed the code to account
> for this, so hopefully your example should work unaltered now.
>
> --Glen
>
> > -----Original Message-----
> > From: Riggs, David [mailto:driggs@asset.com]
> > Sent: Tuesday, August 13, 2002 11:05 AM
> > To: axis-dev@xml.apache.org
> > Subject: RE: Axis Chokes on Complex Types from MS Soap 3.0
> >
> >
> > I ripped the "elementFormDefault='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]
> > > 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
> > >
> > >
> > > >>>>
> > > I have not tried a .NET client, only Axis (which works if
> > > I manually remove the namespace from the generated code)
> > > <<<<
> > >
> > > From what Glen said, it should also work if you manually
> > > remove elementFormDefault='qualified' from the WSDL, right?
> > >
> > > Scott
> > >
> >
>
>
>
>



Mime
View raw message