Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 86824 invoked from network); 4 Sep 2003 00:31:48 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Sep 2003 00:31:48 -0000 Received: (qmail 25020 invoked by uid 500); 4 Sep 2003 00:31:06 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 24923 invoked by uid 500); 4 Sep 2003 00:31:04 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 24896 invoked from network); 4 Sep 2003 00:31:04 -0000 Received: from unknown (HELO hotmail.com) (207.68.163.75) by daedalus.apache.org with SMTP; 4 Sep 2003 00:31:04 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 3 Sep 2003 17:29:47 -0700 Received: from 170.252.136.1 by sea1fd.sea1.hotmail.msn.com with HTTP; Thu, 04 Sep 2003 00:29:46 GMT X-Originating-IP: [170.252.136.1] X-Originating-Email: [gianny_damour@hotmail.com] From: "gianny DAMOUR" To: geronimo-dev@incubator.apache.org Bcc: Subject: Re: [newbie] JMX Console - where to start? Date: Thu, 04 Sep 2003 02:29:46 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Message-ID: X-OriginalArrivalTime: 04 Sep 2003 00:29:47.0406 (UTC) FILETIME=[A52A42E0:01C3727B] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Alex wrote: > > Finally, will your console operate on the JSR-77 objects through > > the MEJB, or will you be sticking to "pure JMX"? If the latter, will >the > > same JSR-77 components be available? > >I'd rather stick to the JMX interface until I know more about the >requirements, but as things are situated now, delegating the JSR-77 >components to a different formatter would be very simple. The components >are already available through the MBeanServer interface. The trick at this >point is just presenting them in a more readable fashion. AFAIK the JSR-77 managed objects are available through the MBeanServer because, OUR implementation defines them as MBean. Based on the JSR-77 specifications, I've got the feeling that these objects are not required to be MBeans: it is not written explicitely that the managed objects MUST be exposed as JMX manageable resources. However, it is written explicitely that the MEJB exposes them as JMX manageable resources. In other words, if one simply writes a JMX agent to interact with the JSR-77 managed objects, then one makes an assumption on the implementation. However, to migrate from a MBeanServer implementation to a MEJB one is simple (if you have a business interface on top of the javax.management.j2ee.Management at least), hence, I assume that by now it is fine. Gianny _________________________________________________________________ Trouvez l'�me soeur sur MSN Rencontres ! http://g.msn.fr/FR1000/9551