aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Persisting second identical object causes ConstraintViolationException? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Persisting second identical object causes ConstraintViolationException?" Watch "Persisting second identical object causes ConstraintViolationException?" New topic
Author

Persisting second identical object causes ConstraintViolationException?

Andre Brandt
Greenhorn

Joined: Feb 28, 2009
Posts: 1
Hi Forum,

first - I'm new to javaee and ejb3 ;)

I've created a new entity bean which has successfully be deployed on my jboss 5.0.0GA. Persisting new objects does work. (via em.persist(object)) So I wrote a little test to find out, if my unique constraint also work - well, it doesn't seem to/it works too good ...

When adding a second, identical object to my database, I get an ConstraintViolationException. Can someone tell me, where my mistake is?

I thought, that, when catching EntityExistsException that should not happen...

best regard,
Dellerium



entity bean:


Dao bean:




Alok Kushwah
Ranch Hand

Joined: Jul 10, 2007
Posts: 31
Looks like program is trying to insert rows with same id. You can see "Unique Key Voilation" error in thread. Query the database table and you can find out row exist or not.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Persisting second identical object causes ConstraintViolationException?