[
https://issues.apache.org/jira/browse/TOMEE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715057#comment-16715057
]
ASF GitHub Bot commented on TOMEE-2060:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/tomee/pull/72
> 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
> Priority: Major
> Labels: pull-request-available
>
> 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
(v7.6.3#76005)
