Had the same problem in the code that executed outside of standard
TransactionInterceptor....
the solution is to wrap your calls to transactions using the following
technique:
| TransactionManager tm;
|
|
| try {
| tm = TransactionManagerProvider.JBOSS_PROVIDER.getTransactionManager();
| } catch (Exception e) {
| throw new RuntimeException(e);
| }
|
| Transaction oldTx = null;
| try {
| oldTx = Transactions.applyBefore(Transactions.TYPE_REQUIRED, tm);
|
| .... do something ....
|
| } catch (TransactionException e) {
| throw new RuntimeException(e);
| } finally {
| try {
| Transactions.applyAfter(Transactions.TYPE_REQUIRED, tm, oldTx);
| } catch (TransactionException e) {
| log.error("", e);
| }
| }
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927941#3927941
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927941
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
