Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-1612

jboss.jms vs jboss.mq for JMSProviderLoader in sample-bindinds.xml

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 4.2.0.GA_CP06, 4.3.0.GA_CP04
    • 4.3.0.GA_CP01, 4.2.0.GA_CP03
    • System
    • None

    Description

      After tidying up sample-bindinds.xml in JBPAPP-996:

      The file correctly refers to JMSProviderLoader in the 'jboss.mq' domain, as this is the default messaging provider in AS 4.2 / EAP 4.2:
      <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"

      In EAP 4.3 this needs to point to 'jboss.jms' for all 4 occurences in the file:
      <service-config name="jboss.jms:service=JMSProviderLoader,name=HAJNDIJMSProvider"

      If the file is patched for producing EAP 4.3 then you can do it there. Otherwise I suppose you can add duplicate definitions using both domain names.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-996 Discrepancies between port schemes in sample-bindings.xml

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              gaohoward Howard Gao
              dandread1@redhat.com Dimitrios Andreadis
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: