This content has been marked as final.
Show 4 replies
-
1. Re: 3.2.x and jaxrpc exceptions
starksm64 Oct 16, 2004 1:36 PM (in response to adrian.brock)That should be correct as the exception would either need to be translated into a simple fault or have a custom serializer.
-
2. Re: 3.2.x and jaxrpc exceptions
adrian.brock Oct 16, 2004 3:17 PM (in response to adrian.brock)There is also a problem with class java.net.URI which doesn't exist in j2se1.3
-
3. Re: 3.2.x and jaxrpc exceptions
starksm64 Oct 16, 2004 6:59 PM (in response to adrian.brock)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.
-
4. Re: 3.2.x and jaxrpc exceptions
thomas.diesler Oct 17, 2004 10:29 AM (in response to adrian.brock)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.