-
15. Re: Re: Portable Naming and Binding of Resources
1 of 1 people found this helpfulThe only good of it is that you have a standard way (according to a few tck tests, since I am not finding anything about such concrete use case in the specs) to bind URLs into JNDI, without that you will need to use something specific to the AS, such as our naming subsystem configuration.
I will keep the support for this feature while restoring the support for "java:" in lookup.
-
16. Re: Portable Naming and Binding of Resources
created two issues
[WFLY-3114] @Resource(lookup="java:...") causes an exception for URL resources - JBoss Issue Tracker
Thanks for your constructive discussion!
Thomas
-
17. Re: Portable Naming and Binding of Resources
thomas.kriechbaum This issue was fixed also by WFLY-2423 PR, which was merged yesterday. Can you check if the issues you create still exist, and update/close these based on what you find out?
-
18. Re: Portable Naming and Binding of Resources
Hello Eduardo,
I have just downloaded build #1040 (25.3.2014 - https://ci.jboss.org/hudson/job/WildFly-latest-master/1040/) and run my tests successfully.
- @Resource(lookup="java:...") works even for URL-Resources
- JNDI-names can be used in jboss specific deplyoment descriptors (e.g. jboss-web.xml) to refer to an URL defined in standalone.xml
I have added comments to both issues (WFLY-3114 and WFLY-3114).
Should I close these issues and refer to WFLY-2423?
Very well done!
Thanks,
Thomas
-