Uploaded image for project: 'TomEE'
  1. TomEE
  2. TOMEE-2935

Naming context should not enforce read only on close

    XMLWordPrintableJSON

    Details

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

      Description

      10.4.4. Container Provider Responsibility

      The container must ensure that the enterprise bean instances have only read access to their environment variables. The container must throw the javax.naming.OperationNotSupportedException from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.

      We can question if close() is modifying the context. But from what TCK does, it looks like no.
      So no need to check read only here. Tomcat does consider it to be a write operation so it fails

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jlmonteiro Jean-Louis Monteiro
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: