[jboss-jira] [JBoss JIRA] (WFLY-3115) JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources

[Thomas Kriechbaum (JIRA)]

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

Thomas Kriechbaum updated WFLY-3115:
------------------------------------

    Summary: JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources  (was: JNDI-Names should be supported in jboss-specific deployment descriptors for URL resurces)

    
> JNDI-Names should be supported in jboss-specific deployment descriptors for URL resources
> -----------------------------------------------------------------------------------------
>
>                 Key: WFLY-3115
>                 URL: https://issues.jboss.org/browse/WFLY-3115
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.0.0.Final
>            Reporter: Thomas Kriechbaum
>            Priority: Critical
>
> When using URL-Resources it would be very helpful, if the jboss-specific deployment descriptor (e.g. jboss-web.xml or jboss-app.xml) allows to reference a JNDI-name. At the moment, only valid URLs are supported.
> When defining JNDI-names (e.g. java:app/url/Configuration) instead of convreate URLs, the EAR must not be adopted for each deployment as the specific URL is part of the server configuration (e.g. standalone.xml).
> see proposal by [~sfcoy] at https://community.jboss.org/message/861952#861952

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