Thanks Mike. I have now seen the earlier discussion.
But Im not sure if it is true. If you decompile the class file (produced by Sun JDK 1.4.2 compiler) then both exceptions are mentioned in the signature.
I state both exceptions in the signature so that the SOAP toolkit knows about the exception and can re-create it on the client. This works with GLUE.
At present I am just getting an AxisFault class re-created on the client.
Mike Perham wrote:
This was discussed about a week ago. Check the archives.
-----Original Message-----
From: Stuart Barlow [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2003 5:02 AM
To: [EMAIL PROTECTED]
Subject: dissappearing exception types from method signature
I have a java interface with the following method...
public String logon(String libraryName, String userName, String domain,
String password) throws DmSystemException, DmInvalidLogonException;
After I run Java2WSDL and WSDL2Java the method has changed to...
public java.lang.String logon(java.lang.String libraryName,
java.lang.String userName, java.lang.String domain, java.lang.String password) throws java.rmi.RemoteException, com.hummingbird.hc.dm.api.DmSystemException;
DmInvalidLogonException derives from DmSystemException which derives from java.lang.Exception
Why has the DmInvalidLogonException dissappeared from the signature?
Thanks, Stuart.
