You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Lenin David Lozano Argel <ld...@avansoft.com> on 2009/01/27 00:52:13 UTC
Geronimo: connectionFactoryJndiName not recognized in MDB EJB 3.0
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.
Re: Geronimo: connectionFactoryJndiName not recognized in MDB EJB 3.0
Posted by David Jencks <da...@yahoo.com>.
On Jan 26, 2009, at 6:42 PM, Lenin David Lozano Argel wrote:
>
> Well, The Oracle OC4J How To MDB 3,0 use these properties.
>
> You can look at
>
> http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-ejb30-mdb/doc/how-to-ejb30-mdb.html
>
> The sample in Oracle Oc4J uses these properties. I don't know how to
> associate the Connection Factory with the MDB in Geronimo or WAS CE.
>
Unfortunately oracle doesn't really make clear where the activation
config properties come from or how to tell which ones can be used.
They come from the inbound messaging resource adapter. Unless you
install something else, in geronimo that's activemq. Each inbound
resource adapter comes with an ActivationSpec class that is a javabean
that indicates the properties you can set on it. A few of these can
also be documented in the ra.xml descriptor for the adapter. The
standard properties for jms inbound adapters are:
The recommended properties for JMS ActivationSpec JavaBean are:
destination
(required), destinationType (required), messageSelector,
acknowledgeMode,
subscriptionDurability, clientId, subscriptionName.
As you can see, the oracle activation spec does not appear to support
destination and uses the decidedly non-standard
connectionFactoryJndiName.
I'll update our documentation to make it clearer where the properties
we use come from. However, the geronimo sample is more likely to be a
useful guide to deploying an mdb on geronimo than the oracle
documentation.
thanks
david jencks
>
>
> Did you find documentation somewhere to support the properties you are
> using?
>
> thanks
> david jencks
>
>
>
> --
> View this message in context: http://www.nabble.com/Geronimo%3A-connectionFactoryJndiName-not-recognized-in-MDB-EJB-3.0-tp21674243s134p21678653.html
> Sent from the Apache Geronimo - Users mailing list archive at
> Nabble.com.
>
Re: Geronimo: connectionFactoryJndiName not recognized in MDB EJB
3.0
Posted by Lenin David Lozano Argel <ld...@avansoft.com>.
Well, The Oracle OC4J How To MDB 3,0 use these properties.
You can look at
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-ejb30-mdb/doc/how-to-ejb30-mdb.html
The sample in Oracle Oc4J uses these properties. I don't know how to
associate the Connection Factory with the MDB in Geronimo or WAS CE.
Did you find documentation somewhere to support the properties you are
using?
thanks
david jencks
--
View this message in context: http://www.nabble.com/Geronimo%3A-connectionFactoryJndiName-not-recognized-in-MDB-EJB-3.0-tp21674243s134p21678653.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Geronimo: connectionFactoryJndiName not recognized in MDB EJB 3.0
Posted by David Jencks <da...@yahoo.com>.
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.
>