[
https://issues.jboss.org/browse/WFLY-3115?page=com.atlassian.jira.plugin....
]
Thomas Kriechbaum commented on WFLY-3115:
-----------------------------------------
I have tested this scenario with wildfly 8.0.1 SNAPSHOT Build #1040 (25.3.2014 -
https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/)
With this build @Resource(lookup="java:app/url/Configuration") and the following
entry in jboss-web.xml resolves an URL defined within standalone.xml
<resource-ref>
<res-ref-name>java:app/url/Configuration</res-ref-name>
<jndi-name>java:jboss/url/Configuration</jndi-name>
</resource-ref>
see WFLY-2423 that covers the appropriate fix.
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
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:jboss/url/Configuration) instead of concrete 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