The default resource adapter name is "ActiveMQ RA" instead of "DefaultActiveMQConnectionFactory"  in your plan.  Try this:



<name:resource-link>ActiveMQ RA</name:resource-link>

On Thu, Dec 15, 2011 at 12:53 AM, random21 <> wrote:
Hi Folks, I've been playing around with with the latest beta release but could succesfully deploy an MDB, using the the Full JEE 6 profile. I'm building an EJB jar. My class implements MessageListener interface and has the @MessageDriven annotation :
@MessageDriven(name = "MessageSinkMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }, mappedName = "jms/queue/MDBSourceQueue")
I have added the same information from the annotation to ejb-jar.xml. (Which I think is not necessary ?) And last but not least, I have added an openejb-jar.xml too. (see below) The latter has a dependency to the activemq rar which comes with G3.0-beta1. As for the MDB, the names the JMS ConnectionFactory to be used. Again, this factory exists by default in G3-beta1. When deploying the jar from Eclipse with the Geronimo Adapter I get an error saying:
No Resource Adapter defined for MDB 'MessageSinkMDB' org.apache.geronimo.common.DeploymentException: No Resource Adapter defined for MDB 'MessageSinkMDB'
Geronimo.log mentions:
[AdminObjectRefBuilder] Failed to build reference to resource env reference [java:comp/BeanManager, java:comp/Validator, java:comp/ValidatorFactory] defined in plan file. The corresponding entry in Geronimo deployment descriptor is missing.
I have tried to add a deployment plan with custom JMS resources and package everyting as an EAR. No luck either. No luck with the Geronimo samples either. Am I missing something too obvious ? Thanks, B openejb-jar.xml:
	xmlns:dep="" xmlns:ejb=""
	xmlns:name="" 	>

View this message in context: MDB in Geronimo 3.0-beta-1
Sent from the Users mailing list archive at