Return-Path: Mailing-List: contact general-help@xml.apache.org; run by ezmlm Delivered-To: mailing list general@xml.apache.org Received: (qmail 64042 invoked from network); 20 Oct 2000 01:09:30 -0000 Received: from chmls06.mediaone.net (24.147.1.144) by locus.apache.org with SMTP; 20 Oct 2000 01:09:30 -0000 Received: from pikachu (estaub.ne.mediaone.net [24.147.194.46]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id VAA15685 for ; Thu, 19 Oct 2000 21:09:29 -0400 (EDT) From: "Ed Staub" To: Subject: RE: Yet another question about creating a Document Date: Thu, 19 Oct 2000 21:18:11 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <003a01c03a2a$02d31800$2d53b8d1@swbell.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N >Really? So Xalan has to use Xerces? We can't tie ourselves to one DOM >parser like that. That's why we've been trying to use the DOM API, so we >can swap parsers at any time. No no no... I didn't say that. I suggest moving this to the Xalan list if you want to follow up. Scott Boag can answer better than I. See http://xml.apache.org/xalan/dtm.html and http://xml.apache.org/xalan/usagepatterns.html#dom-in. In general, Xalan doesn't use a DOM at all unless specifically asked to. This is for performance reasons. If you want to use another (non-Xerces) parser, I think you need to write a Liaison class to it. They're pretty small. -Ed -----Original Message----- From: Eric Hodges [mailto:harmony2@swbell.net] Sent: Thursday, October 19, 2000 8:09 PM To: general@xml.apache.org Subject: Re: Yet another question about creating a Document ----- Original Message ----- From: "Ed Staub" To: Sent: Thursday, October 19, 2000 4:56 PM Subject: RE: Yet another question about creating a Document ... > It might be worth examining other general-purpose code to see whether > requiring the top element at document creation is awkward. I notice that > Xalan dodges the issue by > new org.apache.xerces.dom.DocumentImpl(); > but I'm sure there are other reasons in Xalan's case as well. Really? So Xalan has to use Xerces? We can't tie ourselves to one DOM parser like that. That's why we've been trying to use the DOM API, so we can swap parsers at any time. --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org