Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 70885 invoked from network); 29 Oct 2003 04:35:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Oct 2003 04:35:53 -0000 Received: (qmail 66169 invoked by uid 500); 29 Oct 2003 04:35:25 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 66032 invoked by uid 500); 29 Oct 2003 04:35:24 -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 66019 invoked from network); 29 Oct 2003 04:35:24 -0000 Received: from unknown (HELO smtp005.mail.ukl.yahoo.com) (217.12.11.36) by daedalus.apache.org with SMTP; 29 Oct 2003 04:35:24 -0000 Received: from 82-35-107-109.cable.ubr06.dals.blueyonder.co.uk (HELO yahoo.co.uk) (james?strachan@82.35.107.109 with plain) by smtp1.mail.vip.ukl.yahoo.com with SMTP; 29 Oct 2003 04:35:33 -0000 Date: Wed, 29 Oct 2003 04:35:12 +0000 Subject: Re: anyone any idea how to get the RMI JMX connector running inside Geronimo? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: James Strachan To: geronimo-dev@incubator.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <5C3713B4B134BA49AFEAF154D0A1EE1C2FAE62@mlnexc01.emea.cpqcorp.net> Message-Id: <48E24D5C-09C9-11D8-9956-000A959D0312@yahoo.co.uk> X-Mailer: Apple Mail (2.552) 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 On Tuesday, October 28, 2003, at 07:43 pm, Bordet, Simone wrote: > Hi James, > >> I've started hacking together a simple Swing JMX console for >> Geronimo >> using GroovySwing (more on that another day). But to be able >> to connect >> to a Geronimo server from a remote UI process we need the >> mx4j remote >> connector adapter, such as the JRMP / RMI one thats part of mx4j. > > MX4J will exit soon with a beta for JMX 1.2 and JSR 160. > Since the remoting API you need is already implemented and working > (and standard :) you may want to start directly from JSR 160 API > instead of the old MX4J 1.x remote API. > On the MX4J site you can find online docs on how to use the JSR 160 > API and how to port from MX4J 1.x to JSR 160. Excellent! Thanks. I guess I could use CVS HEAD until the beta's out right? James ------- http://radio.weblogs.com/0112098/