Thanks for your reply. The specification doesnt require the container to handle MDBs, but it seems the Glassfish EJB embedded container loads the Message Queue service, here is an extract from Embedded EJB container log:
INFO: GlassFish v3 (74.2) startup time : Embedded(1638ms) startup services(1185ms) total(2823ms)
Mar 18, 2010 9:04:52 AM com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
INFO: Using com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the delegate
Mar 18, 2010 9:04:52 AM org.glassfish.admin.mbeanserver.JMXStartupService$JMXConnectorsStarterThread run
INFO: jts.startup_msg
Mar 18, 2010 9:05:15 AM com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter setConnectionURL
[b]INFO: JMS Service Connection URL is :mq://localhost:7676/[/b]
Mar 18, 2010 9:05:16 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: DIRECT
Mar 18, 2010 9:05:21 AM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:DIRECT
Mar 18, 2010 9:05:21 AM com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter updateMDBRuntimeInfo
INFO: endpoint.determine.destinationtype
Since Glassfish Embedded EJB container is loading up message queue, I expect it to be able to deploy MDBs.
Otherwise, if it doesnt support MDBs, it should quietly ignore any @MessageDriven classes in the deployed jar, or may be log a warning.
That still helps developers to test their stateless/full ejbs without creating a separate jar for MDBs.
Thus, I think that it might be an issue in glassfish that needs to be addressed.
[Message sent by forum member 'razib']
http://forums.java.net/jive/thread.jspa?messageID=392445