tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (TOMEE-2060) EJB component can modify its naming context
Date Tue, 20 Jun 2017 07:49:01 GMT


ASF GitHub Bot commented on TOMEE-2060:

Github user rmannibucau commented on the issue:
    1. not that much, we are not that strong about it cause we all have different habits and
thinking about it
    2. you can create a new surefire execution for this test with another arquillian container
config, that said the embedded testing in openejb-core (which forks by test) should be enough
    3. you logged it was read only in the assembler, this is enough for now probably

> EJB component can modify its naming context
> -------------------------------------------
>                 Key: TOMEE-2060
>                 URL:
>             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

View raw message