Heads Up:
s:button - always plays first item from list (must be a bug)
h:commandButton - plays selected/clicked item (works properly)
where s is Seam taglib
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073669#4073669
Reply to the post :
My mistake. I had the wrong thread/topic pulled up when I did the post!
Ignore last entry. Admins: please delete my last entry if you can.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073671#4073671
Reply to the post :
This will only work for EntityExistsException due to primary key constraint.
The situation I encountered is with a unique constraint on other columns which
are not primary keys.
I used the setter methods to set some field values, and then handled both
InvalidStateException to retrieve all of
One way to solve it, from my experience, would be to inject another instance of
that bean to itself, and invoke the method (the one annotated with
REQUIRES_NEW) on that injected bean. Otherwise the transaction attributes
annotations have no effect because you're not working with the proxy but
Here's an alternative:
Instead of trying to ignore the exception, try calling em.contains(...) and if
that returns false, then execute em.persist(...).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047060#4047060
Reply to the post :
Even better, try using em.merge(...) instead of em.persist(...). That way if
the entity exists it will be merged and you won't get an exception.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047062#4047062
Reply to the post :
Surely someone has a hint on this. My experience is the transaction
annotations have no effect. -OR- I have misinterpreted something.
My experience: no transactions are committed unless the method in the top
session bean in the call chain exits.
My understanding:
A method annotated with:
