tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Katya Todorova (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-2060) EJB component can modify its naming context
Date Fri, 16 Jun 2017 07:51:01 GMT

    [ https://issues.apache.org/jira/browse/TOMEE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051536#comment-16051536
] 

Katya Todorova commented on TOMEE-2060:
---------------------------------------

PR https://github.com/apache/tomee/pull/72 is just an initial proposal so we have a common
ground for discussion.
I set the naming context to read only at earlier point (when app is created) than on actual
lookup (when ThreadLocal is used)  -IMO, it fits there nicely as the final step of app creation
(though the code could be moved elsewhere).
Let me know what you think?

> 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.4.14#64029)

Mime
View raw message