TransactionRolledbackException obscuring custom exception

Question

I could use some input on the following issue:
I have an Order SSB that uses a Catalog SSB. When the Catalog SSB encounters an (expected) error condition, it throws a CatalogException that extends RemoteException. The message that's stuffed in the CatalogException needs to be passed back to the client. What happens, however, is that the CatalogException gets nested in a TransactionRolledbackException before the Order SSB can process it, so the message is buried in the nested exception.
A couple questions: 1) Is this always the case, i.e., an exception thrown in an SSB is going to get wrapped in a TransactionRolledbackException?
2) Can I get to the message in the nested exception without complicated parsing?
Any input would be appreciated.

Answer 1

You should never use RemoteException - that's more-or-less "reserved" for the server vendor to signal to the application that the remote protocol is not working correctly. Same for EJBException (but that's more of a "my application server is crashing into smoking ruins" exception). If you want to use an exception, create your own subclass from Exception or RuntimeException. Or use one of the "stock" ones, such as IllegalArgument exception. Don't use NullPointerException - that's not a helpful one for an application to throw by itself.
If you're using Container-managed transactions, a subclass of Exception will not automatically roll-back the CMT, whereas a subclass of RuntimeException will. Neither will directly affect a client-initiated transaction.
Oh, and by the way - Exception is a subclass of Throwable, which already implements Serialiable.