Stephen Ting wrote:
Hi,for me here is a subtle difference, since OJBRuntimeException is a subclass of RuntimeException. so if in one component such an exception is thrown, it will just fall throw your catch clause.
I think that's make no different than catching
PersistenceBrokerException because it is the Subclass of OJBRuntimeException.
I dont know the OJB code that well to know whether an OBJBrokerException
can be thrown by the use of the PersistentBroker, but to be on the safe side I would catch OJBRuntimeException. in the end I agree that a PersistentBrokerException should be sufficient according to the javadocs.
so I just tried to see if I can reproduce such an exception, but I see which is wrapped in an application exception and passed correctly to the servlet.
maybe the message I just posted about
old thread: Re: ConnectionFactoryManagedImpl and rollbacks
is of any interest for you.
hope that helps a bit.
best wishes Kristian
Whereas, for my case where I uses OJB in session bean, it's throw RemoteException whenever there is communication link breakdown. The PersistenceBrokerExeption catch in session bean was not propagate to the web container. Hopefully, this is correct.
Cheers, Stephen
-- ---------------------------------------------------------------------- Jentro Technologies GmbH Kristian Meier, Developer ---------------------------------------------------------------------- Rosenheimer Str. 145e 81671 Munich, Germany Tel. +49 89 189 169 80 mailto: [EMAIL PROTECTED] Fax. +49 89 189 169 99 internet: http://www.jentro.com ----------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
