Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 77175 invoked from network); 11 Jan 2002 23:26:14 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Jan 2002 23:26:14 -0000 Received: (qmail 12944 invoked by uid 97); 11 Jan 2002 23:26:20 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 12928 invoked by uid 97); 11 Jan 2002 23:26:20 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 12917 invoked from network); 11 Jan 2002 23:26:19 -0000 Message-ID: <3C3F7538.7090905@yahoo.com> Date: Fri, 11 Jan 2002 23:28:56 +0000 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Phoenix Blocks as MBeans References: <60098A15DB40D511B69F00508B8B84BFD7DD79@hoth.whitehill.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Fred, >I need to be able to remotely manage and monitor both Phoenix and my Blocks >- JMX seemed the most "standards-based" way to do this, and seemed >consistent with the design of Phoenix (to the extent I understand it). > True enough. - PH -- To unsubscribe, e-mail: For additional commands, e-mail: