[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1629) message-destination-link does not work for MDB's

[Adrian B. (JIRA) <jir...@jb...>]

     [ http://jira.jboss.com/jira/browse/JBAS-1629?page=history ]
     
Adrian Brock closed JBAS-1629:
------------------------------

    Resolution: Duplicate Issue

Please test the latest version (including release candidates) 
before reporting bugs.
http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java?r1=1.64.2.9&r2=1.64.2.10
If it doesn't work for you, feel free to reopen the original bug report.

> message-destination-link does not work for MDB's
> ------------------------------------------------
>
>          Key: JBAS-1629
>          URL: http://jira.jboss.com/jira/browse/JBAS-1629
>      Project: JBoss Application Server
>         Type: Bug
>   Components: EJBs
>     Versions:  JBossAS-4.0.1 SP1
>     Reporter: Matthias Germann

>
>
> Setting the message-destination-link child element of the message-driven element does not work on JBoss 4.0.1sp1. JBAS-1130 is related to this but i think that message-destination-link support was only added for the message-destination-ref element but not for the message-driven element.
> A message-driven bean can sspecify the message-destination it want's to listen to with the message-destination-link element (see http://java.sun.com/developer/EJTechTips/2005/tt0322.html#1).
> i.e.:
> <message-driven >
>  <ejb-name>RegEmailSender</ejb-name>
>  <ejb-class>ch.tvfrutigen.chandertaler.ejb.service.RegEmailSenderBean</ejb-class>
>  <messaging-type>javax.jms.MessageListener</messaging-type>
>  <transaction-type>Container</transaction-type>
>  <message-destination-type>javax.jms.Queue</message-destination-type>
>  <message-destination-link>RegEmailsQueue</message-destination-link>
>  ...
> </message-driven>
> It should be possible that the senders of a message and the processing MDBs can link to the same message-destination in the assembly-descriptor. Therefore, only the message-destination in the assembly-descriptor must be mapped to a jndi-name in jboss.xml.
> Setting the message-destination-link elment on JBoss 4.0.1sp1 has no effect. It is still necessary to map the MDB's to the jndi-name of the queue/topic using the destination-jndi-name element. IMHO, it should not be necessary to specify the destination-jndi-name element when using message-destinations.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira