I thought that JAX-RPC interfaces could throw exceptions other than
RemoteException, and that these exceptions would be mapped to SOAP
Faults. But if I add a 'throws IllegalArgumentException' to my interface,
xrpcc balks saying that the exception isn't supported.
Section 14.3.6 shows some mappings between SOAP faults and
Java exceptions. Are these the only legal exceptions that an RPC
service can throw? If I want to indicate an illegal argument was
passed, how to I create a RemoteException that is mapped onto
the rpc:BadArguments SOAP fault, since RemoteException also
maps onto rpc:ProcedureNotPresent? (Or should I even care
how it gets mapped -- will the client see any difference between
the two?)
Mike