Guys, could you please suggest me how you handle attempt to add duplicate
into table in your application?

What's the best way of finding exception which I can handle when thrown
exception consist of bunch of other nested exceptions? Here is example:
http://pastebin.com/m3505bcbc   As you can see topmost is
'RollbackException', but I'm interested in first 'EntityExistsException'
which is real cause. Currently I catch RollbackException, then create List
of all nested exceptions and looking for ones which I know about such as
EntityExistsException. But this approach doesn't seem good to me.

Thanks!
-- 
View this message in context: 
http://n2.nabble.com/Handling-nesting-exceptions-%28EntityExistsException%29-tp1567049p1567049.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Reply via email to