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 80649 invoked from network); 1 Jul 2000 23:10:30 -0000 Received: from e22.nc.us.ibm.com (32.97.136.228) by locus.apache.org with SMTP; 1 Jul 2000 23:10:30 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e22.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id SAA28526 for ; Sat, 1 Jul 2000 18:48:57 -0500 From: rubys@us.ibm.com Received: from d54mta04.raleigh.ibm.com (d54mta04.raleigh.ibm.com [9.67.228.36]) by southrelay02.raleigh.ibm.com (8.8.8m3/NCO v4.9) with SMTP id TAA45184 for ; Sat, 1 Jul 2000 19:10:29 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 8525690F.007F4373 ; Sat, 1 Jul 2000 19:10:03 -0400 X-Lotus-FromDomain: IBMUS To: tomcat-dev@jakarta.apache.org Message-ID: <8525690F.007E58DD.00@d54mta04.raleigh.ibm.com> Date: Sat, 1 Jul 2000 18:55:14 -0400 Subject: Re: Using xerces/jaxp with Tomcat Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I would like propose making JAXP a hard prereq for Tomcat 3.2. There are too many people finding Tomcat difficult to install and use with other Apache projects. It looks like all this would take is the removal of a few lines in JspUtil and XmlMapper. Regarding the following comment in JspUtil: // Will try first to use JAXP, if that fails revert to old method. // This will go away soon - but it's required if you want to use tomcat // inside j2ee ( class conflict, bug - can't use jaxp right now) What is the outlook for this being fixed? If necessary, can we put this code on a separate branch for J2EE? - Sam Ruby