Bug 1019303 - JNDI names validation is too strict
Summary: JNDI names validation is too strict
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Harald Pehl
QA Contact: Jakub Cechacek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 12:52 UTC by Martin Svehla
Modified: 2015-02-01 23:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-03 12:22:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Martin Svehla 2013-10-15 12:52:14 UTC 
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):
EAP 6.2.0.ER5
Comment 1 Martin Svehla 2013-10-15 12:52:58 UTC 
Any changes to this will be probably related to bug 1019241 too
Note You need to log in before you can comment on or make changes to this bug.