[
https://jira.jboss.org/jira/browse/JBMESSAGING-1670?page=com.atlassian.ji...
]
Jeff Mesnil closed JBMESSAGING-1670.
------------------------------------
Resolution: Rejected
the destination name is never used to bind to JNDI.
In JBM 2.x, the JNDI bindings are mandatory and we will never default to the destination
name to bind to JNDI.
Having forward slashes in the destination name is not an issue (see
JMSServerDeployerTest)
Disallow forward slashes in jms destinations
--------------------------------------------
Key: JBMESSAGING-1670
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1670
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Jeff Mesnil
Fix For: 2.0.0
We need to disallow forward slashes in JMS destination names since they won't be able
to be deployed in JNDI since the slash will be interperted as a subcontext by JNDI
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira