consuming .NET webservice with xsd:any

["Planting, Hans" <Ha...@nl.compuware.com>]

Hi there,

I have an application that consumes a .NET webservice using Axis 1.2.1
containing the following construct:

<xsd:complexType>
  <xsd:sequence>
    <xsd:element ref="s:schema"/> <!-- 's' is alias for
http://www.w3.org/2001/XMLSchema -->
    <xsd:any/>
  </xsd:sequence>
</xsd:complexType>

As far as I know neither the JAXRPC 1.1 nor the WSDL 1.1 specification
defines an element having a ref to a 'schema' and Axis does not seem to
generate any specific code for the element. This being a .NET service I
assume the construct is used to represent a DataSet. 
My question is this: is there any support planned or available for dynamic
types like DataSet (eventhough it is not standardized yet) ?? 

Thanks,

Hans


-- 
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it. 

Re: consuming .NET webservice with xsd:any

[Anne Thomas Manes <at...@gmail.com>]

Yes, this represents a .NET Dataset. You should convince the service
provider to convert the Dataset to a defined type.

Anne

On 2/6/06, Planting, Hans <Ha...@nl.compuware.com> wrote:
>
> Hi there,
>
> I have an application that consumes a .NET webservice using Axis 1.2.1
> containing the following construct:
>
> <xsd:complexType>
>   <xsd:sequence>
>     <xsd:element ref="s:schema"/> <!-- 's' is alias for
> http://www.w3.org/2001/XMLSchema -->
>     <xsd:any/>
>   </xsd:sequence>
> </xsd:complexType>
>
> As far as I know neither the JAXRPC 1.1 nor the WSDL 1.1 specification
> defines an element having a ref to a 'schema' and Axis does not seem to
> generate any specific code for the element. This being a .NET service I
> assume the construct is used to represent a DataSet.
> My question is this: is there any support planned or available for dynamic
> types like DataSet (eventhough it is not standardized yet) ??
>
> Thanks,
>
> Hans
>
>
> --
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
> disclose
> it to anyone else. If you received it in error please notify us
> immediately
> and then destroy it.
>
>