[jboss-as7-dev] Strange behaviour with messaging

[Vimal Kansal]

Aren't JMS resources registered with JNDI tree? When I deploy an with 
EJBs, all EJBs are clearly seen as registered in JNDI view, so how come 
the messaging resource which indeed is registered with JNDI tree is not 
getting displayed? When I execute /subsystem=naming:jndi-view, as the 
operation name indicates, shouldn't it show me a view of what exactly is 
registered inside JNDI at a given point in time?

Vimal

On 19/07/2011 5:21 PM, Heiko Braun wrote:
>
> it's two different things: CLI>;jndi-view() does list the actual jndi tree.
> Whereas console>JMS shows the entry names of the messaging subsystem config.
>
> On Jul 19, 2011, at 7:17 AM, Jaikiran Pai wrote:
>
>>>
>>> (2) View of messaging resources from admin console is different from
>>> command line invocation of :jndi-view command
>>> ==========================================================================================================
>>>
>>> In admin console web app, I can see testQueue, testTopic and
>>> ConnectionFactory but when I run /subsystem=naming:jndi-view command
>>> from jboss-admin , these resources are not visible in JNDI tree.
>> Ideally, both the admin console and the CLI should end up using the same
>> operation to list the jndi-view. Probably that's not happening
>> currently. Will take a look later.
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev