No DuplicateKeyException on create

Question

When I call the create method on some home interface, with a key that already exists in the database, I don't get a DuplicateKeyException. Instead a rollback exception occurs when the transaction is committed. This behaviour makes it very difficult to catch the problem early and present the user with a nice message. Does anybody know what can be done about this?

Answer 1

Thanks for your answer. Your solution does mitigate the problem but it doesn't really solve it. I guess it's more general than what I described. I can accept that the PM often doesn't flush changes to the database until commit time, which happens when the business method returns to the container but before the container returns to the client. Any SQL- or JDO exception thrown during this flushing will be logged to the serve log, but the client is only informed that a rollback has occurred. There is no way for the client code to analyze the cause, since the actual exception isn't in the cause chain of the RemoteException thrown to the client.
Wouldn't it be nice if the SQL exception was included in the cause chain of the remote exception. A typical chain would then be:
RemoteException, caused by
RollbackException, caused by
JDODataStoreException, caused by
SQLException
Another nice feature would be if the business method had some way (probably not portable) to force the PM to flush its updates and catch any exceptions.
Any thoughts on this?
- Gunnar