You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tomee.apache.org by "Jean-Louis Monteiro (Jira)" <ji...@apache.org> on 2020/12/07 11:03:00 UTC

[jira] [Created] (TOMEE-2935) Naming context should not enforce read only on close

Jean-Louis Monteiro created TOMEE-2935:
------------------------------------------

             Summary: Naming context should not enforce read only on close
                 Key: TOMEE-2935
                 URL: https://issues.apache.org/jira/browse/TOMEE-2935
             Project: TomEE
          Issue Type: Bug
            Reporter: Jean-Louis Monteiro


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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)