glassfish
  1. glassfish
  2. GLASSFISH-20296

Make endpoint component naming context available during call to endpointDeactivation

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0_b87_RC3
    • Component/s: ejb_container
    • Labels:
      None

      Description

      To handle CONNECTOR_SPEC-4, the Connectors 1.7 spec says the following in Section Para #3 of Section 13.4.4:
      – snip –
      The application server must make the application component environment
      namespace of the endpoint (that is being activated), available to the resource adapter
      during the call to the endpointActivation and endpointDeactivation
      methods. The resource adapter may use this JNDI context to access other resources.
      – snip –

      Though GLASSFISH-19452 provides the naming context during endpointActivation, GF doesn't provide the endpoint naming context to the resource adapter during the call to endpointDeactivation. Please fix this.

        Activity

        Sivakumar Thyagarajan created issue -
        shreedhar_ganapathy made changes -
        Field Original Value New Value
        Assignee amy.yang [ amy.yang ] guojun.shan [ guojun.shan ]
        guojun.shan made changes -
        Assignee guojun.shan [ guojun.shan ] amy.yang [ amy.yang ]
        amy.yang made changes -
        Assignee amy.yang [ amy.yang ] marina vatkina [ mvatkina ]
        marina vatkina made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 4.0_b87_RC3 [ 16116 ]
        Fix Version/s 4.0_b85 [ 16114 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            marina vatkina
            Reporter:
            Sivakumar Thyagarajan
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: