Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 34321 invoked from network); 10 Aug 2002 11:16:46 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Aug 2002 11:16:46 -0000 Received: (qmail 24821 invoked by uid 97); 10 Aug 2002 11:17:09 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 24761 invoked by uid 97); 10 Aug 2002 11:17:08 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 24749 invoked by uid 98); 10 Aug 2002 11:17:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D54F610.9080307@yahoo.com> Date: Sat, 10 Aug 2002 12:16:32 +0100 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon-Phoenix Developers List Subject: Re: Problems testing Phoenix prior to beta. References: <0H0K00CPMJ7VQC@mta5.snfc21.pbi.net> <3D538762.3070608@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1; 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 Alexis, Huw, >> Thanks for providing the earlier information. I downloaded the >> binary release from 8-7 and, sure enough, all the mbeans under the >> phoenix domain were missing. I was able to determine that the >> problem has something to do with the conf/kernel.xml element: >> >> conf/xsl > A complete guess, but it could have something to do with Class.forName(..) use in mx4j.adaptor.http.HttpAdaptor public void addCommandProcessor(String path, String processorClass) { try { HttpCommandProcessor processor = (HttpCommandProcessor)Class.forName(processorClass).newInstance(); addCommandProcessor(path, processor); } catch (Exception e) { log.error("Exception creating Command Processor of class " + processorClass, e); } } Class.forName(..) is bad in complex ClassLoader environments. People should do this.getClass().getClassLoader().loadClass(..) intead. Hmmm, maybe I should visit some of my own code! - Paul -- To unsubscribe, e-mail: For additional commands, e-mail: