Will do as soon as I get back in the office tomorrow.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102666#4102666
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4102666
___
j
I kind of found the answer to this by myself. There is a TransactionFilter
class that is setup in the web.xml for the WSRP service archive. This class
will start a transaction. The comment in the class is that the WSRP runtime
needs transactions so it creates them.
I think there is a problem w
This is for version 2.6.2 of the portal.
I have a question regarding managed transactions. We have developed a portlet
that is using hibernate and it is managing its own transactions. If this is
deployed and viewed locally on a JBoss portal instance everything works ok.
Now the problem. When th
I temporarily solved the issue by writing an EJB3 MDB interceptor that blocks
the execution until the server up signal is available. While not ideal it works
very well.
It would be nice to have the same feature that is already available for EJB2.x
MDBs to the new EJB3 ones though.
Thanks,
Flor
This is on a JBoss-4.0.4 Patch 1.
I know that for non EJB3 MDB you can configure the 'DeliveryActive' attribute
in MDBConfig (in a user defined invoker configuration) and your MDB will be
deployed but not started. Starting it can be done at a later point through JMX.
I browsed through annotatio
