Return-Path: X-Original-To: apmail-geronimo-user-archive@www.apache.org Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 31EF96F95 for ; Tue, 28 Jun 2011 13:18:57 +0000 (UTC) Received: (qmail 69550 invoked by uid 500); 28 Jun 2011 13:18:56 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 69385 invoked by uid 500); 28 Jun 2011 13:18:56 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 69378 invoked by uid 99); 28 Jun 2011 13:18:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 13:18:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xhhsld@gmail.com designates 209.85.212.54 as permitted sender) Received: from [209.85.212.54] (HELO mail-vw0-f54.google.com) (209.85.212.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 13:18:50 +0000 Received: by vws18 with SMTP id 18so186507vws.13 for ; Tue, 28 Jun 2011 06:18:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yChMa5Z9gMkgnJEvjf/mVgyOqHz22wwiIuJkqcgyHsc=; b=la6qV0ILadgrkBHXZh3HNZXnw2KQzJOcS6b6hv9+FXNZzDOjfy1slcjPwsIP8ZYNtt fUoh06eFlsPb/fqr73DrRFucefCVJBzzdefeXKVBkHuY77GYIl356tCUxv4tDRG1+++H r9h29fBbpH0y7Bws4KsBod/TlI8TMAPqpfKVk= MIME-Version: 1.0 Received: by 10.52.177.133 with SMTP id cq5mr5594641vdc.225.1309267110098; Tue, 28 Jun 2011 06:18:30 -0700 (PDT) Received: by 10.52.187.195 with HTTP; Tue, 28 Jun 2011 06:18:30 -0700 (PDT) In-Reply-To: <01E7E8E50C98824E9045DFD5FFC859D42D89DDD02D@SBSRV.ot.local> References: <01E7E8E50C98824E9045DFD5FFC859D42D89DDD021@SBSRV.ot.local> <01E7E8E50C98824E9045DFD5FFC859D42D89DDD02D@SBSRV.ot.local> Date: Tue, 28 Jun 2011 21:18:30 +0800 Message-ID: Subject: Re: Geronimo JMS Topic lookup and usage From: Ivan To: user@geronimo.apache.org Content-Type: multipart/alternative; boundary=20cf3071ca4603783604a6c581bc --20cf3071ca4603783604a6c581bc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable IIRC, while using InitialContextFactory impl from ActiveMQ, it just reads the local properties files, you might double check with AcitiveMQ community. Geronimo does have a JNDI tree, but it is an in-vm one. For querying which topics are deployed, one possible way is by JMX. A corresponding mbean will be registered in MBean server by ActiveMQ once a topic is created on the server side, you might use the jconsole tool from JDK to explore them. Another way from Geronimo side is to use GBean query, while it is a bit complex in my opinion, comparing with JMX. Hope it helps. 2011/6/28 Florian Schaetz > Hello,**** > > ** ** > > > For the ActiveMQ, I think the doc from its website should**** > > > be helpful for you, it describes that how AcitveMQ JNDI **** > > > works. e.g. Dynamically creating destinations section **** > > > explains why an unexisting destination could be lookuped.**** > > > Thanks. One thing I found was=85**** > > ** ** > > =93However, ActiveMQ's JNDI Implementation does NOT talk to the naming > server.=94**** > > ** ** > > So: Is there chance to talk to the naming server and ask, which topics ar= e > deployed?**** > > ** ** > > Regards,**** > > ** ** > > Flo**** > --=20 Ivan --20cf3071ca4603783604a6c581bc Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable IIRC, while using InitialContextFactory impl from ActiveMQ, it just reads t= he local properties files, you might double check with AcitiveMQ community.= =A0Geronimo does have a JNDI tree, but it is an in-vm one.
For querying= which topics are deployed, one possible way is by JMX. A corresponding mbe= an will be registered in MBean server by ActiveMQ once a topic is created o= n the server side, you might use the jconsole tool from JDK to explore them= . Another way from Geronimo side is to use GBean query, while it is a bit c= omplex in my opinion, comparing with JMX.
Hope it helps.

2011/6/28 Floria= n Schaetz <Florian.Schaetz@optitool.de>

Hello,=

=A0

> For the ActiveMQ, I think the doc from its websit= e should

> be helpful for you, it describes that how AcitveMQ JNDI=

> <= span lang=3D"EN-US">works. e.g.=A0Dynamically creating destinations section=

> <= span lang=3D"EN-US">explains why an unexisting destination could be lookupe= d.


Thanks. O= ne thing I found was=85

=A0=

=93However, ActiveMQ's JNDI= Implementation does NOT talk to the naming server.=94=

=A0

So: Is there chance to talk to the naming server and a= sk, which topics are deployed?

=A0

= Regards,

=A0

Flo

=



--
Ivan
--20cf3071ca4603783604a6c581bc--