Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 4319 invoked from network); 28 Oct 2001 02:42:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 28 Oct 2001 02:42:29 -0000 Received: (qmail 17632 invoked by uid 97); 28 Oct 2001 02:42:34 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 17611 invoked from network); 28 Oct 2001 02:42:33 -0000 Message-Id: <200110280242.f9S2gVu04914@mail012.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Ant Developers List" Subject: Re: How does JAXP Factory works? Date: Sun, 28 Oct 2001 11:29:51 +1000 X-Mailer: KMail [version 1.3.1] References: <018701c15e26$c4dab400$0100a8c0@jose> <002101c15f1f$651c4160$d1eefea9@unknownp7vgk60> <027801c15f48$e17ca190$0100a8c0@jose> In-Reply-To: <027801c15f48$e17ca190$0100a8c0@jose> X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 28 Oct 2001 11:38, Jose Alberto Fernandez wrote: > > The version of JAXP shipped with Ant 1.4 is already using the context > > classloader and is the one that is bundled with crimson 1.1.1 bugfix > > release. (Dated from June 26). > > The issue is not the use of the ContextClassLoader but the fact that the > fallback code (when CCL not set or not available -- JDK1.1) seems to me is > wrong. The code will only look on the System classloader, that means there > is no chance for the code to look in the same classloader as where JAXP was > loaded. Which is the only reasonable thing to do IMHO if CCL is not set. I disagree. The only reasonable thing would be to have JAXP act the same regardless of which JVM it is in. JAXP is in the bootclass loader (or is it extensions classloader?) in jdk1.4 and thus can only access System classloader. I think it would be unacceptable that code that worked perfectly well in 1.1->1.3 would break in 1.4 - especially widely used stuff like XML. Theres already enough gotchas and upgrade headaches as there is. -- Cheers, Pete ---------------------------------------------- Money is how people with no talent keep score. ---------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: