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.getTransactionMan
That works great with portlets. As a matter of fact, I was using it already.
However my problem arises when accesing the portal context from a Spring bean
(not referenced by a portlet) or a servlet.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923990#39239
I'm not accessing UserModule but I got the same exception in a portlet when I
tried to use my own SessionFactory, so my solution might apply to your case.
Try to edit jboss-portlet.xml to add a "transaction" element :
|
|
| MyPortlet
|
| Required
|
