Javier Deniz wrote (and I paraphrase):
<<
The EJB server should ensure that the exceptions thrown by a bean
are also covered in the remote interface.
>>
I agree. We will add this to our todo list.
You will notice though, that any exceptions that are not part of
the checked exceptions in the remote interface are automatically
folded into a RemoteException, which is something the caller
should always catch ...
> When I ran my client, I got the following output in my client window:
>
> ==== Begin output
> java myPackage.client.Client
> myPackage.client.Client: Creating a party manager...
> myPackage.client.Client: Obtaining all the parties in the system...
> java.rmi.RemoteException: Unexpected error in
> myPackage.server.PartyMgrBean.getAllParties(). Transaction rolled back.
> java.lang.Exception: Deliberately thrown to check that Weblogic does
> not check for EJB compliency in exception handling. The remote interface
> throws AccessPartyException and the bean throws just an Exception
- Sriram
________________________________________________________________________
Principal Engineer BEA/WebLogic, San Francisco www.weblogic.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
