[jboss-jira] [JBoss JIRA] (WFLY-2070) Allow for deployable JNDI resource file

Tue Sep 17 09:32:03 EDT 2013

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

Lieven Doclo commented on WFLY-2070:
------------------------------------

When you define the JNDI resources in your application xml descriptor or component xml descriptor, you're essentially hardcoding the values in your application deployment (for example, when you want to change the values, you need to change the deployment artifact, which is not convenient). The WildFly subsystem configuration forces you to edit the configuration file (standalone.xml or other) which we can't do in our production environment or use the CLI tooling (which requires WildFly CLI knowledge on every level of deployment). 
I'm not saying it's a big deal, but it would surely be convenient to hot-deploy or change JNDI simple bindings by just dropping or editing a file just like you can do with datasources. It seems like a quick win.
Alternatively, it would be convenient if we could change or add simple JNDI bindings in the Web Management console.

> Allow for deployable JNDI resource file
> ---------------------------------------
>
>                 Key: WFLY-2070
>                 URL: https://issues.jboss.org/browse/WFLY-2070
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Naming
>            Reporter: Lieven Doclo
>            Assignee: Eduardo Martins
>
> It would be nice to have a deployable xml file to add simple JNDI bindings. Something like the *-ds.xml files.
> For example:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <naming>
>   <bindings>
>     <simple name="java:/url/some_url_resource" value="file://..." type="java.net.URL"/>
>   </bindings>
> </naming>
> {code}

--
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