Red Hat Bugzilla – Bug 1019303
JNDI names validation is too strict
Last modified: 2015-02-01 18:00:47 EST
Description of problem:
Form fields for entering JNDI names enforce java:/ or java:jboss/ name prefixes. While this is not incorrect, it's in my opinion too strict. Using no prefix is valid (implies java:comp/env namespace). Eg the user can use just "jms/TestQueue" JNDI name in both CLI or configuration file. I don't think it's necessary to force users to set fully qualified JNDI names.
There are also other valid namespaces: java:global, java:app, java:module and java:comp.
Version-Release number of selected component (if applicable):
Any changes to this will be probably related to bug 1019241 too