Re: use of "xsd:ur-type" for serialization of arrays and structs

SOAP 1.1 specifies this use of type when array elements may be of different 
types.  See section 5.4.2 at 
http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383522.  It was present in 
past revisions of the XML Schema spec, but has now become a concept rather than 
an actual type.  The anyType and anySimpleType are conrete manifestations of 
the ur-type concept.  Yuck.

I will look into this, but unfortunately I do not have time right now.

Does a .NET client handle this exception?

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: "Ingo Fischer" <ingo.fischer@xxxxxxxxxx>
To: <nusoap-general@xxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 12, 2005 8:46 AM
Subject: [Nusoap-general] use of "xsd:ur-type" for serialization of arrays and 
structs


> Hi !
> 
> We have a webservice which is used by some Java-clients using Axis and 
> we have a problem which only occurs at the moment when returning a fault.
> 
> In this case we use an array of soapvals as fault-detail. The returned 
> XML-Message for the fault-detail looks like:
> 
> <detail>
>   <soapVal xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:ur-type[2]">
>    <errorcode xsi:type="xsd:string">5003</errorcode>
>    <message xsi:type="xsd:string">The invalid</message>
>   </soapVal>
> </detail>
> 
> Axis is not able to use the type "ur-type" and don't knows how to map 
> this and cannot find a deserializer for that type.
> 
> The problem is thatin the case of an "unknown" array which will be 
> serialized that in the "serialize_val" method in nusoap_base.class.inc 
> the following line is hard coded:
> 
> $array_typename = 'xsd:ur-type';
> 
> 
> When you look into the Shema definition then a type with the name 
> "ur-type" is NOT defined. On some places there are references to "simple 
> ur-types" or so and there is one line that such a type is named "anyType".
> 
> So we tried to replace the hardcoded type in that line with 
> "xsd:anyType" and Axis was able to correctly read the details and 
> anything wokrs.
> 
> So, why there is hardcoded "ur-type" which is a in fact not existing 
> type and will it be possible to change that to "xsd:anyType" ?
> 
> Ingo Fischer
> 
> -- 
> Ingo Fischer
> _____________________________________________________________________
> 
> Ingo Fischer
> Schlund + Partner AG           NOF-Components : http://www.apollon.de
> Karlsruhe
> Tel.: 0721/91374-0             Secure Internet-Payment:
> http://www.schlund.de                           https://ipayment.de
> _____________________________________________________________________
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Nusoap-general mailing list
> Nusoap-general@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/nusoap-general
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click