[jboss-jira] [JBoss JIRA] Commented: (AS7-1172) JNDI

[Jason Greene (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618648#comment-12618648 ] 

Jason Greene commented on AS7-1172:
-----------------------------------

Initial support for this was included in 7.0.0.Final. John is improving it further for 7.0.1

> JNDI 
> -----
>
>                 Key: AS7-1172
>                 URL: https://issues.jboss.org/browse/AS7-1172
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Naming
>    Affects Versions: 7.0.0.CR1
>            Reporter: Alexandre Gattiker
>            Assignee: John Bailey
>             Fix For: 7.0.1.Final
>
>
> If a JMS destination is created with a JNDI name starting with "/jms/", the JNDI View issues an error message. The destination appears to be up and running fine though.
> <h1>java: Namespace</h1>
> <pre>
>   +- topic (class: javax.naming.Context)
>   |   +- test (class: org.jboss.as.naming.context.ModularReference)
>   +- app (class: javax.naming.Reference)
>   +- module (class: javax.naming.Reference)
>   +- comp (class: javax.naming.Reference)
>   +- queue (class: javax.naming.Context)
>   |   +- test (class: org.jboss.as.naming.context.ModularReference)
>   +- jms (class: javax.naming.Context)
> Failed to lookup: jms, errmsg=Name 'jms' not found in context ''
>   +- global (class: javax.naming.Reference)

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