glassfish
  1. glassfish
  2. GLASSFISH-19252

Add proper support for the platform default connection factory with admin tools

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.0_b72_EE7MS4
    • Component/s: admin_gui
    • Labels:
      None

      Description

      Java EE 7 spec section EE 5.21 defines a "platform default JMS connection factory". This was implemented in GLASSFISH-18899. This means that a connection factory is now always created by default.

      Here is the automatically-created entry that is now created in domaim.xml:

      <connector-connection-pool max-pool-size="64" name="__DefaultJMSConnectionFactory-Connection-Pool" 
          resource-adapter-name="jmsra" connection-definition-name="javax.jms.ConnectionFactory">
      </connector-connection-pool>
          
      <connector-resource pool-name="__DefaultJMSConnectionFactory-Connection-Pool"
          jndi-name="jms/__defaultConnectionFactory" object-type="system-all">
      </connector-resource>
      

      Currently the user will see this in the admin console. The application can look up the default connection factory by using the JNDI name jms/_defaultConnectionFactory (with _ prefix) or using the JNDI name java:comp/DefaultJMSConnectionFactory. However a portable application must use the JNDI name java:comp/DefaultJMSConnectionFactory since that is the name defined in the Java EE 7 specification.

      To avoid confusion, it is desirable if the user didn't actually see jms/__defaultConnectionFactory in the admin console, but saw a special entry which showed the true JNDI name that they need to use.

      Also, the user shouldn't be allowed to delete this connection factory, though they should be allowed to modify it.

      The exact functionality should be decided in conjunction with other interested parties such as the Java EE 7 spec leads and the implementer of GLASSFISH-18899.

        Activity

        Nigel Deakin created issue -
        Tom Mueller made changes -
        Field Original Value New Value
        Tags ee7platspec
        Tom Mueller made changes -
        Description Java EE 7 spec section EE 5.21 defines a "platform default JMS connection factory". This was implemented in GLASSFISH-18899. This means that a connection factory is now always created by default.

        Here is the automatically-created entry that is now created in domaim.xml:

        {noformat}
        <connector-connection-pool max-pool-size="64" name="__DefaultJMSConnectionFactory-Connection-Pool" resource-adapter-name="jmsra" connection-definition-name="javax.jms.ConnectionFactory"></connector-connection-pool>
            <connector-resource pool-name="__DefaultJMSConnectionFactory-Connection-Pool" jndi-name="jms/__defaultConnectionFactory" object-type="system-all"></connector-resource>
        {noformat}

        Currently the user will see this in the admin console. The application can look up the default connection factory by using the JNDI name {{jms/__defaultConnectionFactory}} (with {{__}} prefix) or using the JNDI name {{java:comp/DefaultJMSConnectionFactory}}. However a portable application must use the JNDI name {{java:comp/DefaultJMSConnectionFactory}} since that is the name defined in the Java EE 7 specification.

        To avoid confusion, it is desirable if the user didn't actually see {{jms/__defaultConnectionFactory}} in the admin console, but saw a special entry which showed the true JNDI name that they need to use.

        Also, the user shouldn't be allowed to delete this connection factory, though they should be allowed to modify it.

        The exact functionality should be decided in conjunction with other interested parties such as the Java EE 7 spec leads and the implementer of GLASSFISH-18899.
        Java EE 7 spec section EE 5.21 defines a "platform default JMS connection factory". This was implemented in GLASSFISH-18899. This means that a connection factory is now always created by default.

        Here is the automatically-created entry that is now created in domaim.xml:

        {noformat}
        <connector-connection-pool max-pool-size="64" name="__DefaultJMSConnectionFactory-Connection-Pool"
            resource-adapter-name="jmsra" connection-definition-name="javax.jms.ConnectionFactory">
        </connector-connection-pool>
            
        <connector-resource pool-name="__DefaultJMSConnectionFactory-Connection-Pool"
            jndi-name="jms/__defaultConnectionFactory" object-type="system-all">
        </connector-resource>
        {noformat}

        Currently the user will see this in the admin console. The application can look up the default connection factory by using the JNDI name {{jms/__defaultConnectionFactory}} (with {{__}} prefix) or using the JNDI name {{java:comp/DefaultJMSConnectionFactory}}. However a portable application must use the JNDI name {{java:comp/DefaultJMSConnectionFactory}} since that is the name defined in the Java EE 7 specification.

        To avoid confusion, it is desirable if the user didn't actually see {{jms/__defaultConnectionFactory}} in the admin console, but saw a special entry which showed the true JNDI name that they need to use.

        Also, the user shouldn't be allowed to delete this connection factory, though they should be allowed to modify it.

        The exact functionality should be decided in conjunction with other interested parties such as the Java EE 7 spec leads and the implementer of GLASSFISH-18899.
        Tom Mueller made changes -
        Fix Version/s 4.0_b66 [ 15655 ]
        Tom Mueller made changes -
        Assignee Tom Mueller [ tmueller ] Anissa Lam [ anilam ]
        Anissa Lam made changes -
        Fix Version/s 4.0_b72_EE7MS4 [ 16101 ]
        Fix Version/s 4.0_b66 [ 15655 ]
        Component/s admin_gui [ 10588 ]
        Component/s admin [ 10589 ]
        Anissa Lam made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Anissa Lam
            Reporter:
            Nigel Deakin
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: