Hi,
I have a java class exposed as a web service and one of the methods takes
a Long object (vs. the primitive long) as an argument.
This doesn't work very well with .NET
The JAX-RPC expects the namespace to be:
http://schemas.xmlsoap.org/soap/encoding
but .NET sends it in:
http://www.w3.org/2001/XMLSchema
Of course, the server returns an error in this case.
However, if I change the parameter to be "long" (the primitive) instead
then JAX-RPC expects the
http://www.w3.org/2001/XMLSchema and .NET seems
to work with it.
I was wondering why if someone could comment on why JAX-RPC expects
different namespaces for Long vs. long. I suspect this will also be the
case for all other types, e.g. Integer vs. int, Boolean vs. boolean, etc.
Any solutions if I cannot change Long to long?
Thanks for your help.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net