File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes ejb3 and mdb Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "ejb3 and mdb" Watch "ejb3 and mdb" New topic
Author

ejb3 and mdb

John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
I'm trying to develop an ejb3 mdb and deploy to a weblogic 10
server. I've use the following 2 web sites as models for my
bean:

http://www.oracle.com/technology/tech/java/ejb30.html
http://www.manning.com/panda/

The only change I made was from a topic to a queue. Everything
compiles fine and deploys fine. However, after deployment and I
activate my bean, I get the following error:

The Message Driven Bean, JJGTestMDB does not have a Message Destination
configured. The message destination must be set using a message-destination
link, a destination-resource link or destination-jndi-name.

In my code, I have javax.jms.Queue and jms/QueueConnectionFactory set
the same way he has them set in the Topic example. Can anyone suggest
where I may need to do?

Thanks,

John
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10102
    
165

Please post your MDB code including the annotations. I looked at the example and there's seems to be a typo in that example:



As far as i know, this should have been



Note the propertyName is "destination".


[My Blog] [JavaRanch Journal]
John Gregory
Ranch Hand

Joined: Oct 05, 2006
Posts: 115
Jaikiran,

Is there someplace that has all the ActivationConfigProperty
names? It seems that there are way too many choices to put
in one ejb book (I'm using EJB3 In Action as a ref).

Thanks,

John
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10102
    
165

The properties actually depend on the application server and the jms provider. As per the EJB3 xsd:


The activation-config-property-name element contains the name for an activation configuration property of a message-driven bean. For JMS message-driven beans, the following property names are recognized: acknowledgeMode, messageSelector, destinationType, subscriptionDurability
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: ejb3 and mdb