"rollback" for non-transaction objects

Question

Hello,
I have the following situation:
When I work with some entity in DAL layer it is atached, so all my changes will be flushed. After flushing some contraint of DB can be violated. My changes can be done in transaction or without any transaction, and here is my problem:
If it is in transaction, I should not rollback it (user can correct "mistake"); If it is out of transaction - it should be "rollbacked".
To handle situation with transaction I've made my exception '@ApplicationException' and it works.
But it is bad for the second situation, without transaction. In this case my data are flushed anyway (if exception thrown is ApplicationException). In my exception handler I tried to do this: "if I'm not in transaction so service.getEntityManager.clear();", but data are flushed anyway...
So how to handle this situation? Does "clear()" for non-transaction have to work as "rollback()" for transaction?
(I think that it could be done so: throw ApplicationException if I am in Transaction, otherwise RuntimeException to rollback any changes; but maybe there is another solution?)
Thanks in advance,
Maxym

Answer 1

If you use CMT EJBs, then you do not have to begin, commit, or roll back.
          If your client calls methods that can throw application exceptions, then you
          must handle the transaction (commit or roll back) in the cases that those
          application exceptions are thrown.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "TH Lim" <[email protected]> wrote in message
          news:3a3989d6$[email protected]..
          >
          > Hi,
          >
          > Part of my client code looks like this,
          > try {
          > ..
          > trans.begin(); // transaction begins
          > .. // calling some EJB methods
          > ..
          > trans.commit(); // transaction commits
          > }
          > catch(Exception e)
          > {
          > }
          >
          > My question is do I have to explicitly do a trans.rollback() if there is a
          RemoteException thrown between begin() and commit(). Do I have to
          instantiate a new transaction if the current transaction is rollbacked?
          Thank you.