Creation of an existing entity bean does not throw a CreateException

Question

Hi.
I am using update 1 with oracle 9i thin driver. I am currently working on a unit test that handles CreateExceptions if creation of a duplicate entity occurs. To test this I preloaded my db and then tried in my code to create an entity with the same primary key (a String). When I executed this test what I got back was not a CreateException but rather TransactionRollbackException with a nested SQLException that complained about a constraint violation (my primary key constraint). Looking at the logs it appears the that Persistance Manager or Transaction Manager just marched right on and tried to enter the db row even though a duplicate key was found.
I should see a createException right? Here is my table:
CREATE TABLE CREDIT_CARD (
ID VARCHAR(10) NOT NULL,
CONSTRAINT PK_CREDIT_CARD PRIMARY KEY (ID)
and my test code:
CreditCardLocalHome home = (CreditCardLocalHome)new javax.naming.InitialContext().lookup("java:comp/env/ejb/local/CreditCard");
home.create("key");
home.create("key");
and this is the relavant error trace:
[23/Nov/2003:01:40:29] SEVERE ( 5605): EJB5071: Some remote or transactional roll back exception occurred
com.sun.jdo.api.persistence.support.JDODataStoreException: Got a JDBC SQLException. Please read the remaining error stack for more information.
NestedException: java.sql.BatchUpdateException: ORA-00001: unique constraint (APP.PK_CREDIT_CARD) violated
FailedObjectArray: [CreditCardEJB1720332142_JDOState@1c737be]
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeUpdateBatch(SQLStoreManager.java:1644)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeBatch(SQLStoreManager.java:1559)
at com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.updatePersistent(SQLStateManager.java:997)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:1251)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.notifyBeforeCompletion(TransactionImpl.java:1115)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.commitBefore(TransactionImpl.java:743)
at com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.beforeCompletion(TransactionImpl.java:646)
at com.sun.ejb.containers.ContainerSynchronization.beforeCompletion(ContainerSynchronization.java:105)
at com.sun.enterprise.distributedtx.J2EETransaction.commit(J2EETransaction.java:183)
at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:310)
at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:1809)
at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1608)
at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:529)
at CreditCardEJB1720332142_ConcreteImpl_LocalHomeImpl.create(CreditCardEJB1720332142_ConcreteImpl_LocalHomeImpl.java:34)
at jasper.test_jsp._jspService(_test_jsp.java:69)
As you can see I call the test via a jsp and that the transaction never seems to be mark as rollback. As a result the Persistance Manager tries to enter the row and fails.
Any thoughts?
Matt

Answer 1

Hi, I'm having the same problems, but my table has several constraints (primary key, foreign key, and unique key) set up. I need to know exactly which constraint was violated so that I can return the inputted data that caused the violation in the error message (e.g. "Card No. 1234 already exists" or "User ABCD already exists").
I want to avoid using vendor-specific code to catch the exception (which is thrown as a persistence manager exception), then later extract the parent exception (which I would try to cast as an SQLException and then work from there).
If I follow marina's suggestion, then this means that I need to perform a findBy<myConstraintKey> method for every unique or primary key constraint I have set for my table. Is there another alternative? My concern is how this would affect application performance. Thanks.