Yes, that fixes the problem.
It will now use the old "Standard Message Driven" if there is no messaging-type
which in turns means it will assume an old JMS deployment, i.e. JMSContainerInvoker
(which is now implemented via the JBossJMS MEF).
When you next update the snapshot for the metadata project, it will be fixed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096948#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...