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 63216 invoked from network); 13 Oct 2000 10:43:43 -0000 Received: from web116.yahoomail.com (205.180.60.89) by locus.apache.org with SMTP; 13 Oct 2000 10:43:43 -0000 Received: (qmail 26202 invoked by uid 60001); 13 Oct 2000 10:43:41 -0000 Message-ID: <20001013104341.26201.qmail@web116.yahoomail.com> Received: from [141.202.248.55] by web116.yahoomail.com; Fri, 13 Oct 2000 03:43:41 PDT Date: Fri, 13 Oct 2000 03:43:41 -0700 (PDT) From: Davanum Srinivas Reply-To: dims@yahoo.com Subject: Re: [Xalan2] TrAX, serialize packages moved! To: cocoon-dev@xml.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Thanks Scott for the fixes and the heads-up. FYI to the list, Will post patches for the package names in a short while. -- dims --- Scott_Boag@lotus.com wrote: > > OK, I decided not to do org.apache.xapi.trax.* etc... the package names > were just too damned long for me to bear. They are moved to > org.apache.trax and org.apache.serialize. I don't much like > org.apache.serialize, esp. with org.apache.xml.serialize lurking in the > Xerces classes. But this is just a temporary thing until these APIs move > into full standardization. > > Be warned again: TrAX, and the serialize package will go through some > major changes as they move through the standardization process. I'll try > to make this as smooth as possible, but it's the price we're gonna have to > pay for general standards, and being on the cutting edge of these. I think > it's a price worth paying. This will happen pretty quickly, probably > within a couple of months. When it does happen, I'll try and do it in one > fell swoop, rather than incrementally. Until the true standards go in, > org.apache.trax and org.apache.serialize should be stable. > > I also removed all the special backwards compatibility classes for XalanJ1. > These may go back in at a later date, perhaps in a side directory, but for > now they were cluttering up things, giving the wrong impression about which > classes to use, and increasing our testing matrix. > > The problem with prefix events kept me from doing any performance tuning > the last couple of days, as I had planned. Therefore, it's going to be > 'till Monday or Tuesday before we come out with the Alpha release. I > really don't want to release Alpha without the performance being better > than it is. > > -scott > ===== Davanum Srinivas, JNI-FAQ Manager http://www.jGuru.com/faq/JNI __________________________________________________ Do You Yahoo!? Get Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/