Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 66658 invoked from network); 5 Jul 2000 05:50:49 -0000 Received: from 46-78-127-216.ip.sirius.com (HELO listserv.servlets.com) (216.127.78.46) by locus.apache.org with SMTP; 5 Jul 2000 05:50:49 -0000 Received: (qmail 25977 invoked from network); 5 Jul 2000 05:48:10 -0000 Received: from unknown (HELO collab.net) (192.168.1.41) by 192.168.1.41 with SMTP; 5 Jul 2000 05:48:10 -0000 Message-ID: <3962CB24.C5FA178C@collab.net> Date: Tue, 04 Jul 2000 22:44:04 -0700 From: Jason Hunter X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: ja,en,de,es,pdf MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Using xerces/jaxp with Tomcat References: <8525690F.007E58DD.00@d54mta04.raleigh.ibm.com> <3962B784.847FB0FD@eng.sun.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > Right now the only reason to have the non-jaxp fallback is to support the > case where JAXP is not available. I am happy with requiring JAXP - it will > simplify everything. If we require it, then let's just make sure we ship with it. -jh-