3.2.x and jaxrpc exceptions

[adrian.brock]

Thoms or Scott,

The 3.2.x backported jaxrpc exception implementations are assuming the
java.lang.RuntimeException from java 1.4

Am I correct in assuming that moving
Throwable cause;
to the exception objects (because there is no such thing on RuntimeException in j2se1.3)
doesn't cause a serialization problem because they are serialized into xml?

[starksm64]

That should be correct as the exception would either need to be translated into a simple fault or have a custom serializer.

[adrian.brock]

There is also a problem with class java.net.URI which doesn't exist in j2se1.3

[starksm64]

This was just a duplicate registration of the xsd:anyURI type to use the java.net.URI class instead of the org.apache.axis.types.URI class so I removed it and the jaxrpc module now compiles under jdk1.3.

[thomas.diesler]

A server exception is transported as a element with a well defined semantics. In theory it sould not contain a cause, stack trace, etc. - not even the java class name, since the client may have mapped the fault to a different exception in a different package. The fault QName is important.