I suggest you look at the jms-mdb sample:

http://cwiki.apache.org/GMOxDOC21/sample-applications.html

You specify the resource adapter in a geronimo plan like this:

            <enterprise-beans>
                <message-driven>
                    <ejb-name>OrderRecvMDB</ejb-name>
                    <resource-adapter>
                        <resource-link>jms-resources</resource-link>
                    </resource-adapter>
                </message-driven>
            </enterprise-beans>


You need these properties in the annotations:

@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "OrderQueue")

Did you find documentation somewhere to support the properties you are using?

thanks
david jencks


On Jan 26, 2009, at 3:52 PM, Lenin David Lozano Argel wrote:


Hi.

I develop an EKB 3.0 Message Driven Bean, and the @MessageDriven annotation
is configured like this

@MessageDriven(
                activationConfig = {
                                @ActivationConfigProperty(
                                    propertyName="connectionFactoryJndiName",
propertyValue="jms/SuraBrokerResponseConnectionFactory"),
                        
                    @ActivationConfigProperty(
                            propertyName="destinationName",
propertyValue="jms/QueueResponse"),

                                @ActivationConfigProperty(
propertyName = "destinationType", propertyValue = "javax.jms.Queue"
                                
                )},
                messageListenerInterface = javax.jms.MessageListener.class
                )


When I try to deploy the MDB in Geronimo or WASCE, throws an exception

Unable to create activation spec: No setter found for the activation spec
properties: [connectionFactoryJndiName, destinationName]


Any suggestions?

Thanks.


--
View this message in context: 
http://www.nabble.com/Geronimo%3A-connectionFactoryJndiName-not-recognized-in-MDB-EJB-3.0-tp21674243s134p21674243.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.


Reply via email to