[jboss-jira] [JBoss JIRA] Updated: (AS7-1210) Messaging subsystem binds JMS destinations to java:

[jaikiran pai (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated AS7-1210:
------------------------------

    Affects Version/s: 7.0.0.Final
      Forum Reference: http://community.jboss.org/message/613662#613662  (was: http://community.jboss.org/message/613662#613662)


> Messaging subsystem binds JMS destinations to java:
> ---------------------------------------------------
>
>                 Key: AS7-1210
>                 URL: https://issues.jboss.org/browse/AS7-1210
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.0.0.CR1, 7.0.0.Final
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> As per the discussion in this mail thread http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/002890.html:
> {quote}
> 1) Unqualified relative names like "DefaultDS" or "jdbc/DefaultDS" 
> should be qualified relative to "java:comp/env", "java:module/env", or 
> "java:jboss/env", depending on the context.
> {quote}
> So in case of JMS destinations configured in the standalone.xml/domain.xml, JNDI entries like these:
> {code:xml}
>            <jms-destinations>
>               <jms-queue name="testQueue">
>                  <entry name="queue/test"/>
>               </jms-queue>
>               <jms-topic name="testTopic">
>                  <entry name="topic/test"/>
>               </jms-topic>
>            </jms-destinations>
> {code}
> should bind under java:jboss/ namespace. 
> Instead, currently the org.jboss.as.messaging.jms.AS7BindingRegistry binds it to java: namespace.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira