jms-spec
  1. jms-spec
  2. JMS_SPEC-31

change javadoc on session.createQueue and createTopic to make clearer the provider may create a physical destination

    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

      Most users have been asking us to add a flag to just create the server's side queue with some default values.

      If I add the flag the configuration won't be spec compliant in some people's interpretation as the javadoc says the createQueue / createTopic is not for the physical creation itself.

      I'm not sure what to make on the javadoc, the current version says this:

      "Note that this method is not for creating the physical queue. The physical creation of queues is an administrative task and is not to be initiated by the JMS API. The one exception is the creation of temporary queues, which is accomplished with the createTemporaryQueue method."

      My proposal is to change it to something permissive where the provider may or not create the physical queue. That would be a design choice.

        Activity

        clebertsuconic created issue -
        clebertsuconic made changes -
        Field Original Value New Value
        Summary Allow session.createQueue and createTopic to create server side destinations case they don't exist change javadoc on session.createQueue and createTopic to make clearer the provider may create a physical queue
        clebertsuconic made changes -
        Summary change javadoc on session.createQueue and createTopic to make clearer the provider may create a physical queue change javadoc on session.createQueue and createTopic to make clearer the provider may create a physical destination
        clebertsuconic made changes -
        Description Currently there's a TCK test for Queue and Topic, validating that createQueue or createTopic should throw an exception case the destination is not pre-configured.

        Most users have been asking us to add a flag to just create the server's side queue with some default values.

        If I add the flag the configuration won't be spec compliant.


        IMO, we should just allow the broker to create the server's side destination when a createQueue or createTopic is called.


        It should be up to the implementors to decide upon security restrictions if the user has the permission to




        I'm not sure what to make on the javadoc, the current version says this:

        "Note that this method is not for creating the physical queue. The physical creation of queues is an administrative task and is not to be initiated by the JMS API. The one exception is the creation of temporary queues, which is accomplished with the createTemporaryQueue method."



        My proposal is to change it to something permissive where the provider may or not create the physical queue. That would be a design choice.
        Most users have been asking us to add a flag to just create the server's side queue with some default values.

        If I add the flag the configuration won't be spec compliant in some people's interpretation as the javadoc says the createQueue / createTopic is not for the physical creation itself.


        I'm not sure what to make on the javadoc, the current version says this:

        "Note that this method is not for creating the physical queue. The physical creation of queues is an administrative task and is not to be initiated by the JMS API. The one exception is the creation of temporary queues, which is accomplished with the createTemporaryQueue method."



        My proposal is to change it to something permissive where the provider may or not create the physical queue. That would be a design choice.
        Nigel Deakin made changes -
        Tags pd20-forreview
        Nigel Deakin made changes -
        Tags pd20-forreview
        Nigel Deakin made changes -
        Tags pd20-minor
        Nigel Deakin made changes -
        Tags pd20-minor
        Nigel Deakin made changes -
        Tags pd20-veryminor
        Nigel Deakin made changes -
        Tags pd20-veryminor ed20-added pd20-veryminor
        Nigel Deakin made changes -
        Tags ed20-added pd20-veryminor ed20-added
        Nigel Deakin made changes -
        Tags ed20-added
        Nigel Deakin made changes -
        Tags pd20-added
        Nigel Deakin made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Nigel Deakin [ nigeldeakin ]
        Resolution Fixed [ 1 ]
        Nigel Deakin made changes -
        Fix Version/s 2.0PD [ 16049 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved: