Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 67913 invoked from network); 6 May 2009 07:10:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 May 2009 07:10:03 -0000 Received: (qmail 1168 invoked by uid 500); 6 May 2009 07:10:03 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 1112 invoked by uid 500); 6 May 2009 07:10:03 -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 1092 invoked by uid 99); 6 May 2009 07:10:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2009 07:10:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xasima@gmail.com designates 209.85.218.163 as permitted sender) Received: from [209.85.218.163] (HELO mail-bw0-f163.google.com) (209.85.218.163) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 May 2009 07:09:52 +0000 Received: by bwz7 with SMTP id 7so5495081bwz.19 for ; Wed, 06 May 2009 00:09:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=P4Iay9f/RIqsNhAAuhiFpJ29QwOTXDs2h++u3GkYIiw=; b=mQ7YVyZMQWsBsUdZNrcZMNH5Cv0L8yUoP2RY5/VyyGaaiHXxc71ciIl9x+xSFMftoQ UTUkfDv8/nwvv0s797pg9/kY66kY0TaKlXPQzB+iQ9SuCbi1CYdBHH3KWnLUFN6ExUUJ Q66oAqFgAAE/vzhSRBigruQC2inQdTjERCiJE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=LfMZJ1ZwZP/XWWCA6m+W08UxJw8Mm3fBod2t8vwtkMID/iUNNL+KscykF7L4MZn2mI eFw6z37kDeZa4tlrZp3HdVr4YC5bJtZa0obEAIHDIJJJ4ZjnkDhoOG14/s6dr5th+g3Q 9i6s9Wdezj0Jvl/0ImQVG5t7iz2o1g4GaEbzY= MIME-Version: 1.0 Received: by 10.103.168.5 with SMTP id v5mr667248muo.77.1241593770106; Wed, 06 May 2009 00:09:30 -0700 (PDT) Date: Wed, 6 May 2009 09:09:30 +0200 Message-ID: <7d6453040905060009u17ae872ci8c5a9fe1f3bb6c75@mail.gmail.com> Subject: JMS MBean in geronimo From: Xasima Xirohata To: user@geronimo.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi. What is the simplest way to develop and expose mbeans (gbean) to monitor a particular EJB 3.0 Bean. Could we, for example, perform this in a manner (*) that use @Management, @Depends annotations. (*) http://mastertheboss.com/en/jboss-server/44-jboss-mbeans-pojo.html?tmpl=component&print=1&page= Actually it is seems that we have no wiki article in geronimo -2.2 on the developing and exposing MBeans (Gbean) with EJB 3.0 assistance. Although the same example (as by link above) could be realized by @Resource injection of the target EJB to gbean + placing dependency in EJB to transfer their lifecycle methods to target GBean. Would someone hint how to perform this in most elegant way? -- Best regards, ~ Xasima Xirohata ~