You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Katya Todorova (JIRA)" <ji...@apache.org> on 2017/06/09 13:21:18 UTC

[jira] [Created] (TOMEE-2060) EJB component can modify its naming context

Katya Todorova created TOMEE-2060:
-------------------------------------

             Summary: EJB component can modify its naming context
                 Key: TOMEE-2060
                 URL: https://issues.apache.org/jira/browse/TOMEE-2060
             Project: TomEE
          Issue Type: Bug
          Components: TomEE Core Server
    Affects Versions: 7.0.3
            Reporter: Katya Todorova


According to the Java EE specification (6/7) EE.5.3.4:
The container must ensure that the application component instances have only
read access to their naming context. 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.

It seems that IvmContext checks if the naming context is read-only and throws the corresponding exception but the flag is false by default and is never changed.
Is this done on purpose or is this a todo functionality?  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)