I was looking a little deeper: In JCA 1.5 Spec, Page 12-54:
When the message-driven bean is deployed, the bean deployer chooses an appropriate resource adapter based on the type of the message listener it supports. (Note: tag <messaging-type> in the MDB Deployment Descriptor) So Jboss should : 1- not WARN if there is no <message-driven-destination> in a MDB Deployment Descriptor, because it's not EJB 2.1 2- not WARN if there is no <message-destination-type> in a MDB Deployment Descriptor, because it's optionnal 3- bind correctly a MDB to a RA if in the MDB-DD there is a <messaging-type> tag equal to this RA-DD tag: <connector> | <resourceadaper> | <inbound-resourceadapter> | <messageadapter> | <messagelistener> | <messagelistener-type> | </messagelistener-type> | </messagelistener> | </messageadapter> | </inbound-resourceadapter> | </resourceadaper> | </connector> Thanks -- Mansuy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850117#3850117 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850117 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
