Uploaded image for project: 'JBoss ESB'
  1. JBoss ESB
  2. JBESB-3951

Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Done
    • 4.12
    • 4.11 CP3
    • Transports
    • None

    Description

      org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters.

      The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB.

      1) The constructor needs to pass along JMS credentials to it's parent.
      2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names).

      These can be implemented with the following code snippets:

      >>> In the class declarations <<<
      private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString();

      >>> Replace the 'short' constructor with this longer one <<<
      super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential());

      >>> Implement 'replyDestinationName' with conditional <<<
      private static String replyDestinationName(JMSEpr toEpr)
      throws URISyntaxException
      {
      if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE"))

      { return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString(); }

      else

      { return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString(); }

      }

      Attachments

        Issue Links

          Activity

            People

              tcunning@redhat.com Thomas Cunningham
              rhn-support-rick Rick Wagner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: