jms-spec
  1. jms-spec
  2. JMS_SPEC-94

Define what characters are valid in a durable (or shared subscription) name

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 2.0PD, 2.0
    • Labels:
      None

      Description

      The JMS 1.1 specification does not specify what characters are valid in a durable subscription name.

      It is proposed that the JMS 2.0 specification defines a minimum set of characters which are valid in a durable or non-durable subscription name.

      This is needed to allow portable applications to be created. It is also needed because EJB_SPEC-41 states that if a MDB is defined with subscriptionDurability set to Durable but subscriptionName is not set then the container will automatically set subscriptionName to a suitably unique global name of the MDB, and the container vendor needs to be sure that the name it generates will always be a legal subscription name.

        Activity

        Hide
        Nigel Deakin added a comment -

        In addition, the JMS 2.0 should specify the minimum length of durable subscription name that a JMS provider should support.

        Show
        Nigel Deakin added a comment - In addition, the JMS 2.0 should specify the minimum length of durable subscription name that a JMS provider should support.
        Hide
        chris.barrow added a comment - - edited

        Issue JMS_SPEC-90 "Provide simpler mechanism to refer to queues and topics in a portable way" is related. Could we deal with that issue at the same time? It could easily be resolved by stipulating the same rules for queue and topic names as those proposed for durable subscription name (minimum set of characters and length that must be supported), as noted in a comment I added to that issue.

        Show
        chris.barrow added a comment - - edited Issue JMS_SPEC-90 "Provide simpler mechanism to refer to queues and topics in a portable way" is related. Could we deal with that issue at the same time? It could easily be resolved by stipulating the same rules for queue and topic names as those proposed for durable subscription name (minimum set of characters and length that must be supported), as noted in a comment I added to that issue.
        Hide
        Nigel Deakin added a comment -

        This issue is resolved in the JMS 2.0 final release. Marking issue as resolved with a "fix version" of 2.0

        Show
        Nigel Deakin added a comment - This issue is resolved in the JMS 2.0 final release. Marking issue as resolved with a "fix version" of 2.0

          People

          • Assignee:
            Unassigned
            Reporter:
            Nigel Deakin
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: