Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 20694 invoked from network); 8 Feb 2001 12:06:30 -0000 Received: from mail12.svr.pol.co.uk (195.92.193.215) by h31.sny.collab.net with SMTP; 8 Feb 2001 12:06:30 -0000 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by mail12.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14QpqE-0004ja-00 for cocoon-dev@xml.apache.org; Thu, 08 Feb 2001 12:06:26 +0000 Received: from modem-1.north-dakota.dialup.pol.co.uk ([62.137.85.1] helo=hydrogen) by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14QpqD-00048T-00 for cocoon-dev@xml.apache.org; Thu, 08 Feb 2001 12:06:26 +0000 Received: from paulr by hydrogen with local (Exim 3.20 #1 (Debian)) id 14Qppu-00009C-00 for ; Thu, 08 Feb 2001 12:06:06 +0000 Date: Thu, 8 Feb 2001 12:06:05 +0000 From: Paul Russell To: Cocoon-dev Subject: Re: [C2] Latest CVS does not build. Message-ID: <20010208120605.C29595@hydrogen.internal.luminas.co.uk> Reply-To: Paul Russell References: <20010208112142.B29595@hydrogen.internal.luminas.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: <20010208112142.B29595@hydrogen.internal.luminas.co.uk>; from paul@luminas.co.uk on Thu, Feb 08, 2001 at 11:21:42AM +0000 Sender: Paul Russell X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N * Paul Russell (paul@luminas.co.uk) wrote : > I'm just downloading the relevent API from sun to make sure I fix the > right thing, but if any of you are up, and know the javax.xml.parsers > API inside out, then... Okay, now fixed. Can you guys give it a good checking over, and make sure it works properly? I've checked all the examples, except the ESQL logicsheets and actions, since I don't have a database set up for testing atm. The solution I've implemented is not ideal (read: not as quick as it could be) because I'm having to create a document to get a DOMImplementation, and then in turn use that to create a Document with the right doctype. I can't think of a quicker way of doing this at the moment. I've put a shortcut route on the no-param newDocument, which short-circuits this stage and creates a document directly from the factory. I've also modified the demo web app to use the JaxpParser as its default now. Incidently, shouldn't it be JAXPParser? It's an acronym, right? P. -- Paul Russell Email: paul@luminas.co.uk Technical Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order. Web: www.luminas.co.uk