To get the transaction do Transactions.instance() - you need to ask on e.g. an
EJB3 forum about how to control transactions inside a CMT.
You need to ask on the hibernate forum about why .flush() doesn't commit the
transaction if you are curious.
View the original post :
I posted a solution on the new forum:
Transactions.instance().commit();
| Transactions.instance().begin();
This works, but I am not confident that this is considered clean and proper.
Posting to the EJB3 forum doesnt seem appropriate given that these are seam
managed transactions and my
Thats just fine.
They are seam managed but backed by JTA CMT which are EJB3 provided.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129949#4129949
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4129949
Most excellent! Thanks for putting my mind at ease.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129976#4129976
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4129976
___
I've got about the same problem as you ,
and found the sollution for your part
handling BMT
a) components.xml switch of transactions (see seam manual)
|core:init debug=@debug@ jndi-pattern=@jndiPattern@
transaction-management-enabled=false/ !--
Bump...
Can someone point me at some documentation, or an example of how to
1) mark a Seam POJO's action method to not be transactional (is it sufficient
to add @Transactional(NEVER) annotation?
2) and then how to start and commit a manual user transaction in a way
compatible with an
anonymous wrote :
| You need to use a bean-managed transaction (BMT) bean if you want to
control the transaction - i.e. tx.begin() tx.commit() etc.
|
As I suspected :). Can you point me to what I need to do to declare bean
managed persistence? My backing bean is just a POJO/Seam
anonymous wrote :
| I am using EJB3/JPA persistence and am having trouble with a manually
flushed transaction. Even after a call to em.flush(), the data is not visible
to an external db client -- it seems that even though manually flushed, the
transaction is not committed until after the
