[TOMEE-2935] Naming context should not enforce read only on close

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.0.6
• Assignee: Unassigned
• Reporter: Jean-Louis Monteiro
• Created: 07/Dec/20 11:02
• Updated: 07/Dec/20 11:05
• Resolved: 07/Dec/20 11:05

Description

10.4.4. Container Provider Responsibility

The container must ensure that the enterprise bean instances have only read access to their environment variables. 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.

We can question if close() is modifying the context. But from what TCK does, it looks like no.
So no need to check read only here. Tomcat does consider it to be a write operation so it fails