Hi Glen, Thomas a comment on your first question, since it seems to be very closely related to what we are trying to do as well.
At 11:31 AM 3/25/2002 -0500, Glen Daniels wrote: >Hi Thomas: > >I have a couple of questions relating to the dynamic stuff you're doing >with Axis. > >1) For Axis to successfully deserialize XML into parameters suitable for >passing to a method invocation, we need to know the schema types of the >XML elements. We can either get that information from the xsi:type >attribute, or via metadata (i.e. introspecting the Java class, deployment >info, etc). Do you rely on xsi:type being set for your stuff to work? It >seems like the introspection we do (used to be in RPCElement, now in >ServiceDesc) wouldn't pick up your "real" class and instead would get >metadata for whichever class you specified in the deployment for the >service... so how would you know how to deserialize untyped XML otherwise? In our case the ideal solution would be to use literal encoding, and send the parameters with their tags qualified by their namespaces. Then on the server side you have access to the QName of the parameter type and can easily use the standard Axis typemapping to map it to a deserializer. This is however, currently not done by the proxies generated by WSDL2Java (i.e. the parameter tags are sent without namespace and xsi:type info) when literal encoding is used, which I reported on an earlier posting to this list, and hence it is impossible for the RPCProvider to determine what type is being sent across. /Thomas Thomas Sandholm <[EMAIL PROTECTED]> The Globus Project(tm) <http://www.globus.org> Argonne National Laboratory
