I did make changes to my applications and made it throw
a subclass of java.lang.Exception. I got the same problem as
the one you have reported.
Then i extended that class from RemoteException and still continued
to get the same error !
However when i added a getMessage() method to the sub class, xrpcc
started to function correctly immaterial of the fact whether i was
extending the class from Exception or RemoteException.
refer to 6.4.4 (sub section : "Encoded Fault")
of the JAX RPC specifications(version 0.6).
(I could not find this section in version 0.8 !!!)
The reason for this "may be" that .... "by default, JAX-RPC
can only serialize classes (other than those specified
in the standard JAVA-XML type mapping)which are of type
JAVA Beans. Such serializers marshall these Beans type classes
(classes with getters and setter) into XML-complexTypes".
May be the same applies to Exceptions (Exception classes).
However this explaination may not be correct for i havent
yet really studied the Exceptions related part in the specs.
Hrishikesh
-----Original Message-----
From: YAWN,MICHAEL (HP-Cupertino,ex1) [mailto:mike_yawn_at_HP.COM]
Sent: Thursday, April 11, 2002 10:09 PM
To: JAXRPC-INTEREST_at_JAVA.SUN.COM
Subject: Re: Can interfaces thrown exceptions? (Other than
RemoteException ?)
OK, that makes sense. I'll avoid RuntimeException subclasses.
But I get the same error if I just add Exception to my method
signatures -- xrpcc reports 'java.lang.Exception not supported'.
Any ideas? I've been working with the EA1 release, but just
updated to EA2 to see if it would help with this and other
problems I'm having. Doesn't seem to affect this one (haven't
yet tried the others).
Mike
> -----Original Message-----
> From: Hrishikesh Bhagwat [mailto:Hrishikesh.Bhagwat_at_XORIANT.COM]
> Sent: Wednesday, April 10, 2002 9:05 PM
> To: JAXRPC-INTEREST_at_JAVA.SUN.COM
> Subject: Re: Can interfaces thrown exceptions? (Other than
> RemoteException ?)
>
>
> Hi Mike,
>
> Refer the following lines from JAX-RPC 0.8 spec (Section 5.2.1)
>
> "A service specific exception declared in a remote method
> signature must be
> a checked
> exception. It must extend java.lang.Exception either directly
> or indirectly
> but must
> not be a RuntimeException."
>
>
> IllegalArgumentException extends from a RuntimeException.
> Thats your problem
>
> Hrishikesh
>
>
> -----Original Message-----
> From: YAWN,MICHAEL (HP-Cupertino,ex1) [mailto:mike_yawn_at_HP.COM]
> Sent: Wednesday, April 10, 2002 10:39 PM
> To: JAXRPC-INTEREST_at_JAVA.SUN.COM
> Subject: Can interfaces thrown exceptions? (Other than
> RemoteException?)
>
>
> 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
>