xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Fell <s...@zaks.demon.co.uk>
Subject Re: xml-soap and xsi:type requirements
Date Sat, 12 Aug 2000 16:24:06 GMT
On Fri, 11 Aug 2000 23:04:28 -0400, in soap you wrote:

>> Is there some way to improve this by using reflection?
>> I am *really* impressed by the absolutely seemless nature of the MS ASP+
>> implementation.
>There's no magic in the world .. they either use the SDL file or they
>use assumptions. I believe its the prior ..
>We can do the same if there was a NASSL description of the service -
>the automatically generated serializer/deserializer doesn't bother
>to look at any xsi:type attributes to know what to do .. it just
>knows  because it knew the rules followed during code generation.
>That's gotta be how theirs work.
>Here we're talking about a compromise situation where we don't assume
>a full specification is available but allow some leeway to the user.

for the ASP+ server end, they use the type information packaged with
your code, this metadata drives the server end, and the server can be
asked to return the SDL dynamically from this metadata. There is a
client proxy generator that is driven by the SDL data for writing


View raw message