This isn't entirely true:
Only raw RuntimeExceptions should be wrapped in EJBException. Checked exceptions won't be. Checked or Unchecked exceptions annotated with @ApplicationException won't be either. If they are, it is a bug in our impl. In certain transactional situations, things are wrapped in a EJBTransactionRolledBackException, but this is to inform the client that a rollback occured.
Also, the proposed final just added a <application-exception> element to the ejb-jar.xml deployment descriptor. This is a way to specify that third-party. We don't support it yet though.
Don't know if this helps or not. let me know
This does help. I will use the annotation specified. Thank you.
Can you prevent EJBTransactionRolledBackException from being returned to the client? I do not wish the client to know if a rollback has occurred in certain situations.