[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1807) JBMESSAGING-1667 breaks existing functionality

[Howard Gao (JIRA)]

    [ https://jira.jboss.org/browse/JBMESSAGING-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534746#action_12534746 ] 

Howard Gao commented on JBMESSAGING-1807:
-----------------------------------------

What I have given in the comments in JBMESSAGING-1667 about the reason why it works with MDB containing forward slashes in its destination config is wrong. The real reason why it works is that the destination's JNDIName attribute must be defined. For example, if you deploy a queue with name example/tests/myqueue/ver1, you must specify its jndiName attribute.

So to restore this behavior, we simply ignore those destinations with a JNDIName attribute defined in the 'forward slash checking' code.


> JBMESSAGING-1667 breaks existing functionality
> ----------------------------------------------
>
>                 Key: JBMESSAGING-1807
>                 URL: https://jira.jboss.org/browse/JBMESSAGING-1807
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.SP3.CP09
>            Reporter: Justin Bertram
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP11
>
>
> The fix for JBMESSAGING-1667 breaks existing functionality.  The specific functionality that it breaks is an MDB listening to a non-existent destination whose name contains multiple '/' characters.  When the MDB is deployed the container creates a temporary destination on the MDB's behalf.  Please restore this functionality.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira