Argh. I thought I replied to this weeks ago. Trying again, as I still need
help to get away from using RPC/encoded and use RPC/literal instead.
Service Endpoint interface:
| package com.mycompany.tws;
|
| import java.rmi.Remote;
| import java.rmi.RemoteException;
| import com.mycom
I have a web service using JBoss 4.0.2. I am generating the WSDL and jax-rpc
mapping file using wscompile in rpc/literal mode. I am having problems on the
server with the deserialization of objects that contain arrays of Java Strings.
The SOAP message that is being generated by the client see
Thanks for the reply.
Regarding the multiple declarations of the package/namespace mapping in the
jaxrpc mapping file, I don't know why that is happening. My only guess is that
it comes from the fact that the service endpoint has three methods. I'm only
dealing with one right now, but there i
A little more info. Part of my original problem went away when I changed the
name of the single member data field in my custom exception. It was named
"message," which was causing problems because of a JBoss exception
serialization bug detailed here:
http://www.jboss.org/index.html?module=bb
Thanks for that tip. I've changed my setup so that both the wsdl and the
jax-rpc mapping file are being generated with wscompile, and I changed the
encoding style to RPC/LITERAL. My client is still not properly generating the
custom exception thrown by the web service endpoint, but it looks di
I am trying to get custom exceptions working from a web service on JBoss 4.0.2.
The custom exception is being written into the SOAP response properly, at
least to my eyes, but it is not being deserialized properly by the client. It
comes across as an AxisFault with no cause or detail. The det
