[gzhuye]

I got some confusion when I experimented on MDB application: Why not to put destination-jndi-name into ejb-jar.xml(@ejb.xx tag)?

When we create MDB, we define destination-jndi-name like this:

In JBoss:

* @jboss.destination-jndi-name
* name = “queue/MdbQueue”

In Weblogic:

*@weblogic.message-driven
* destination-jndi-name = “queue/MdbQueue”

Consequently, this configure will be put in the vendor’s config file.

Actually, every MDB has a relevant destination, if we put destination-jndi-name in ejb-jar.xml (using @ejb.xxx tag for destination-jndi-name), so destination-jndi-name can be independent from vendors.

I’m not sure if what I’m say is exactly right, Please give some comments.

Meanwhile, I don’t know if it is a right place to discuss this topic, but I hope everyone in MyEclipse team is very willing to take this topic.

Thanks alot

Paul

[Riyad Kalla]

Paul,
If you are asking for people’s opinions then this is the perfect forum for it. I will ask our EJB guy if he has any comments, but no promises 😉

[gzhuye]

Thank you very much!

I’m waiting for your opinions.

[Greg]

Paul,

I don’t much experience with MDBs and JMS. Have you looked at our tutorials on the subject?
http://www.myeclipseide.com/images/tutorials/MDB/MDB_tutorial.htm

[Author]

Posts