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] [Updated] (TOMEE-2060) EJB component can modify its naming context
Date Fri, 09 Jun 2017 17:51:18 GMT

     [ https://issues.apache.org/jira/browse/TOMEE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Katya Todorova updated TOMEE-2060:
----------------------------------

That would be nice, the only tricky thing would be the alignment of the
defaults since tomcat by default is compliant with the spec (exception is
thrown).

On Fri, Jun 9, 2017 at 5:58 PM Romain Manni-Bucau (JIRA) <jira@apache.org>



> 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)

Mime
View raw message