Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-4305

Support destination lookup by JNDI name in resource adapter

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.7.0
    • Fix Version/s: 5.9.0
    • Component/s: JCA Container
    • Labels:
      None
    • Patch Info:
      Patch Available

      Description

      Use Case:

      A standalone ActiveMQ broker is integrated with a Java EE 6 server (e.g. JBoss AS 7.1, GlassFish 3.1) via activemq-rar-5.7.0.rar.

      Admin objects corresponding to queues or topics are created at server level, assigning a JNDI name in addition to the physical destination name.

      MDBs are used to handle incoming messages from ActiveMQ destinations. The destination is specified by

      @ActivationConfigProperty(propertyName = "destination", propertyValue = "physical-destination-name")

      Problem:

      The physical destination name is now hard-coded in the application. Thus, it is not possible to deploy the unchanged application in a different runtime environment where the given destination has a different physical name.

      Possible solution:

      Create a new activation config property named "destinationJndiName". If this property is set, the destination is supposed to be registered in JNDI with the name given by the property value. When this property is set, both "destinationType" and "destination" are not required.

        Attachments

        1. AMQ-4305.patch
          3 kB
          Harald Wellmann

          Activity

            People

            • Assignee:
              ceposta Christian Posta
              Reporter:
              hwellmann Harald Wellmann
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: