hmm, can you give it a try on the 1.6.0-SNAPSHOT to check it is not a regression but "a merge error" please?
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/3/12 ymaraner <[email protected]> > I have a number of MDBs that were originally developed as EJB2.1 MDBs. They > were upgraded to 3.x MDBs by modifying the version of the deployment > descriptor. > > When I deploy them to 1.5.1 or an early snapshot of 1.5.2, they are invoked > when an appropriate message is posted on the JMS Queue. > > When I deploy them to 1.5.2-SNAPSHOT-80, they are never invoked and there > are no errors or warnings produced even though an appropriate message is > posted on the JMS Queue. > > What changed in 1.5.2 that would prevent this from working? > > Is there a work-around? > > My activation-config looks like this in the ejb-jar.xml file: > > > > > ----- > - Tim > -- > View this message in context: > http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
