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 65286 invoked from network); 29 Jul 2000 18:49:27 -0000 Received: from e22.nc.us.ibm.com (32.97.136.228) by locus.apache.org with SMTP; 29 Jul 2000 18:49:27 -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 OAA25956 for ; Sat, 29 Jul 2000 14:26:56 -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.92) with SMTP id OAA30694 for ; Sat, 29 Jul 2000 14:49:25 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 8525692B.00676406 ; Sat, 29 Jul 2000 14:49:18 -0400 X-Lotus-FromDomain: IBMUS To: cocoon-dev@xml.apache.org Message-ID: <8525692B.00676287.00@d54mta04.raleigh.ibm.com> Date: Sat, 29 Jul 2000 14:49:00 -0400 Subject: Re: C2 status 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 N. Sean Timm wrote: > > Yes...unfortunately, the current version of Xalan 2 doesn't seem to > work at all converting that sitemap, so I can't test any of my code > changes until that starts working. I fired a message off to Scott > to see if I could get some assistance on the Xalan end of things. > I believe the changes I've made are correct, however, so it should > be good to go as soon as we can get Xalan usable. I haven't created > the TraxTransformer yet, but I've modified the necessary files to > make Cocoon2 use (and compile with) Xalan 2. DOMUtils has been > modified to utilize JAXP and TRaX, so there isn't a hard-coded > dependency on Xerces and Xalan anymore. (Although Xalan is > currently the only TRaX implementation that I know of...) Will any of these changes work with Xalan 1? For example, shouldn't the JAXP change be independent of this? Personally, I would like to see the changes go in incrementally, and only the parts which are actually held up by Xalan 2 development be held back. - Sam Ruby