xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksander Slominski <as...@cs.indiana.edu>
Subject Re: xml-soap and xsi:type requirements
Date Sat, 12 Aug 2000 06:14:06 GMT
Sanjiva Weerawarana wrote:

> 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.


i also think that there is no way that even with XML schema that the server
will be able to dispatch calls to overloaded methods unless there are xsi:type
attributes specifying parameter types. considering this the question is how to
enhance Apache SOAP to support MS SOAP requests.

i have experimented with processing MS SOAP requests and it seems that simple
addition to SOAPMappingRegistry will allow to handle such requests:

     SOAPMappingRegistry {
        void registerMethodSignature(QName methodName, Method javaMethod,
     boolean force);

such registered method signature may be used to reconstruct signature of the
method passed in MS SOAP request. the only limitation is of course that it
still will not deal with overloaded methods except that it may throw exception
if user tries to registerMethodSignature() of already registered methodName.
this method allows also to map method names between XML schema and actual java
method name, for example through call:

     Class cls = obj.getClass();
     Method javaMethod = cls.getDeclaredMethod("getInfo, Class[]
     smr.registerMethodSignature(new QName("urn:object","GetInfo"),
     javaMethod, true);

we have mapping of "GetInfo" into "getInfo" method.

such function should allow to register all method signatures from deployment
descriptor and will be necessary to support handling of MS SOAP calls (method
mappings can definitely be expressed as a part of the deployment descriptor).

Aleksander Slominski, Lindley Hall 130, IU, http://www.cs.indiana.edu/~aslom
Don't let what you cannot do interfere with what you can do. ---John Wooden

View raw message