Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
7.0.3
-
None
Description
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?
Attachments
Issue Links
- links to