> We've had a problem related to this. Knowing what you had
> stated below
> about beans throwing RemoteException (or any kind of
> RuntimeException), we
> created our own application exception. We threw it from our
> Entity Bean
> expecting our caller (a Session Bean) to be able to
> gracefully catch it.
> However, our container (WebLogic 4.5) intercepted it and printed the
> exception and stacktrace to the log. This was odd enough, but if this
> occurred within the scope of the transaction, WL rolled the
> transaction
> back! It appeared to rethrow the exception because our
This can happen if the remote interface doesn't declare the application
exception, as in
public interface Interface extends EJBObject {
void method() throws RemoteException;
}
public class Bean implements SessionBean {
public void method() throws ApplicationException {
throw new ApplicationException();
}
}
The container catches the ApplicationException but cannot rethrow it, so it
wraps it in a RemoteException.
- Avi
--
s/\be(\w+)/e-\1/g;
===========================================================================
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".
