[jboss-jira] [JBoss JIRA] (WFLY-3239) Changing the JNDI bound values in the naming subsystem requires reload.

[Eduardo Martins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960880#comment-12960880 ] 

Eduardo Martins commented on WFLY-3239:
---------------------------------------

Such management operation is to "add" new binds, and similar to the standard JNDI operation, adding an entry that already exists should fail, to prevent errors, which by the way, are quite common as results of "human" administration.

So at most this could be a feature request for a new management operation, or as [~brian.stansberry] mentioned, consider an attribute or header to use rebind instead of bind, yet honestly I don't like the idea. JNDI support in Java EE is limited, it provides an environment to Java EE applications, which (ideally) should not be modified during runtime. This kind of configuration should be done before runtime.

[~brian.stansberry], WildFly 8 support for Context#rebind() does not restart services, only updates the existent service value. EAP 6 behaves as you mentioned, rebind() will recreate the service, which leads to restart of any dependent.
                
> Changing the JNDI bound values in the naming subsystem requires reload.
> -----------------------------------------------------------------------
>
>                 Key: WFLY-3239
>                 URL: https://issues.jboss.org/browse/WFLY-3239
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Naming
>    Affects Versions: 8.0.1.Final
>         Environment: All
>            Reporter: Jay Kumar SenSharma
>            Assignee: Eduardo Martins
>
> - Changing the values which are binded in the naming subsystem shows "reload-required", which it ideally should not.  The JNDI naming should follow the "rebind" feature of InitialContext.   The values should be rebinded in the JNDI.
> - Ideally the  JNDI value should not have required the reload and in the runtime only the JNDI value should have changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira