Hi Thomas:
> 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. Can you give me a concrete example of what you're talking about? I'm pretty sure the parameters are being sent with the correct namespaces, but you're right there are no xsi:types. We should still deal fine with this using the literal support Tom and I have put in over the past few weeks. --G
