[jboss-jira] [JBoss JIRA] (AS7-2755) java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only

[David Lloyd (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd resolved AS7-2755.
------------------------------

    Resolution: Rejected


This is because the "java:" context is indeed read-only.  This is actually something that the EE specification mandates, because it heavily impacts the container's ability to perform automatic dependency resolution.  That said, there has been some discussion about allowing binding to "java:" in certain circumstances, and also some discussion about creating a new context URL scheme (like "jndi:" or "user:" or something) which is fully writable (but which cannot be used for dependency injection).

So, that said, we would entertain enhancement requests for one or both solutions.
                
> java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
> --------------------------------------------------------------------------------
>
>                 Key: AS7-2755
>                 URL: https://issues.jboss.org/browse/AS7-2755
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EE
>    Affects Versions: 7.1.0.Beta1
>         Environment: Windows 7/ 32 bit
>            Reporter: Nick .
>            Assignee: David Lloyd
>            Priority: Blocker
>              Labels: InitialContext,, JNDI,, binding
>
> InitialContext context = new InitialContext();
> context.bind('xxxx',yyyy);
> Produces an exception as follows.
> java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira