"adrian(a)jboss.org" wrote : I'll be able to sleep a lot easier when this (and many other properly defined and stable integration points) exists and EJB3 uses it. :-) The integration point in EJB3 is JMSDestinationFactory. 4 supplies a DestinationManagerJMSDestinationFactory, 5 has a ServerPeerJMSDestinationFactory. It isn't how it should be yet, so any criticism is appreciated. n * m is currently 2, and that's about the max we can handle, so I've already dropped support for AS 4.0.5. I need have the separate EJB3 binary plugin asap to solve the n*m problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033380#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...