Bug 1019303

Summary:	JNDI names validation is too strict
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Martin Svehla <msvehla>
Component:	Web Console	Assignee:	Harald Pehl <hpehl>
Status:	CLOSED NOTABUG	QA Contact:	Jakub Cechacek <jcechace>
Severity:	medium	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	brian.stansberry, hbraun, hpehl, jkudrnac, msvehla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-03 12:22:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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