3 Replies Latest reply on Dec 24, 2009 9:52 AM by jaikiran pai

    EJBTHREE-1978: No additional activationConfigProps for message-dest-link

    Andrew Rubinger Master

      @see https://jira.jboss.org/jira/browse/EJBTHREE-1978




      <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          TODO https://jira.jboss.org/jira/browse/EJBBOOK-6 Update the Schema
          to 3.1
            In this section we'll configure our MessageSendingEJB to use a
              This will match the value of @Stateless.name upon our bean
              implementation class
              Declare the Message Destination Reference which will be used in
              the bean implementation class as a logical reference to which
              we'll send messages
            <!-- Assume in jboss.xml we link this to a physical target mappedName -->
            Now we'll configure our MDB to receive messages from the logical
            name defined by the message-destination-link
          Declare the Message Destination which is used as a logical name for


      ...we've got enough metadata to associate the MDB with an underlying physical target (via the message-destination-link), so we shouldn't need activation config properties upon @MessageDriven.


      The solution Jaikiran and I discussed was to resolve the link to the physical mapping during deployment, and set the metadata accordingly.


      Open question: what do do in case of conflicts (ie. both logical name and activationConfigProps are specified but don't match?).  My suggestion to obey the activation config props and log a warning.


      Full example in EJBBOOK-13.