Return-Path: Mailing-List: contact general-help@xml.apache.org; run by ezmlm Delivered-To: mailing list general@xml.apache.org Received: (qmail 49383 invoked from network); 10 Nov 2000 15:38:44 -0000 Received: from lotus2.lotus.com (192.233.136.8) by locus.apache.org with SMTP; 10 Nov 2000 15:38:44 -0000 Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA24566 for ; Fri, 10 Nov 2000 10:41:44 -0500 (EST) From: David_Marston@lotus.com Received: from cammail08.lotus.com (CAMMAIL08.lotus.com [9.95.4.164]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id KAA19219 for ; Fri, 10 Nov 2000 10:38:14 -0500 (EST) Subject: Re: Advice To: general@xml.apache.org X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: Date: Fri, 10 Nov 2000 10:38:12 -0500 X-MIMETrack: Serialize by Router on CAMMAIL08/CAM/M/Lotus(Release 5.0.5 |September 22, 2000) at 11/10/2000 10:38:14 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Dane Foster asks: >I would like to know if Xalan J2 is the path I should take or Xalan J1. >The code I'm writing will be deployed in a production environment so >stability is an import consideration, but I'm also trying to be as >forward looking as possible, and I know further Xalan J1 development >has stopped. It's very hard to say "development has stopped" for open-source software, because new contributors could step forward at any time. However, contributors should find that the Xalan J2 code is easier to get into. The criterion about stability for production use would tip the balance toward Xalan J1 for the next couple months at least. If your need for stability is really timed for Q1 of 2001 or later, then you can think about J2, but we all have to wait and see. I gather that your stylesheets don't encounter any of the (rather few) known bugs in J1, so they might well be vanilla enough for a pre-Gold edition of J2. If you're just writing those stylesheets now, use J1 to test them. If you're writing your own XSLT extensions, use the J2 codebase as you develop them. .................David Marston