xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Snell" <jsn...@lemoorenet.com>
Subject RE: xml-soap and xsi:type requirements
Date Fri, 11 Aug 2000 22:56:44 GMT
This is another good approach, one that I'd like to see researched
further -- but there is still the need for communicating the necessary data
types to the client side -- something that the MS ASP+ implementation does
via SDL and Schemas, thus the appearance of a seemless architecture.

-----Original Message-----
From: rubys@us.ibm.com [mailto:rubys@us.ibm.com]
Sent: Friday, August 11, 2000 1:35 PM
To: soap-dev@xml.apache.org
Subject: Re: xml-soap and xsi:type requirements




Sanjiva Weerawarana wrote:
>
> - if the xsi:type attribute is null, then use the QName of
>   the element as the type and look up a deserializer for  it.
> - the user indicates the serializer by writing in the
>   deployment descriptor this mapping (similar to what (s)he
>   does now for the type QName).

Is there some way to improve this by using reflection?

I am *really* impressed by the absolutely seemless nature of the MS ASP+
implementation.

- Sam Ruby




Mime
View raw message