This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I know of these 3 InvalidTransactionException : This exception indicates that the request carried an invalid transaction context. Transaction attributes mismatch fro example. TransactionRequiredException This exception indicates that a request carried a null transaction context, but the target object requires an activate transaction. If the target object has an attribute of Required, but is not invoked in the right context. TransactionRolledbackException This exception indicates that the transaction associated with processing of the request has been rolled back, or marked to roll back. CMR's created in on Tx context and invoked in another for example.
Hi Akasmat, I appreciate your efforts but I don't think you got the gist of my question. I'm not asking for a description of particular exception but a master list of all the exceptions that I need to know for the exam. Thanks.
The main exceptions you have to know for the exam are five application exceptions: * CreateException * RemoveException * FinderException * ObjectNotFoundException * DuplicateKeyException and... EJBException and RemoteException and... NoSuchObjectException NoSuchObjectLocalException You should also know about TrasactionRollbackException / TransactionRolledbackLocalException and TransactionRequiredException / TransactionRequiredLocalException You should know about NamingException and IllegalStateException. You should know the circumstances under which something can throw an exception, and *especially* you must know the implications of an exception. Application Exception: no rollback, bean lives. If you want a rollback, YOU need to do it either via your UserTransaction (BMT) or by calling setRollbackOnly() on your context (CMT). System Exception: transaction automatically rolled back, bean is destroyed (without getting an ejbRemove() or unset<something>Context() call, and the exception is logged. In general, if you know what is and is not allowed in the spec, then you can usually figure out which exceptions might be thrown. In other words, it is far more important to know that something WILL throw an exception rather than to know exactly which exception is thrown. The Application exceptions are the ones where you should know the exact circumstances under which these exceptions can be thrown, and what it might mean to the bean and to the client. cheers, Kathy