Return-Path: Delivered-To: apmail-xml-commons-dev-archive@xml.apache.org Received: (qmail 97909 invoked by uid 500); 3 Jan 2003 16:26:59 -0000 Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list commons-dev@xml.apache.org Received: (qmail 97886 invoked from network); 3 Jan 2003 16:26:59 -0000 Received: from e34.co.us.ibm.com (32.97.110.132) by daedalus.apache.org with SMTP; 3 Jan 2003 16:26:59 -0000 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e34.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id h03GR0pS021642; Fri, 3 Jan 2003 11:27:00 -0500 Received: from d25ml01.torolab.ibm.com (d25ml01.torolab.ibm.com [9.26.6.102]) by westrelay04.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id h03GUhv3170052; Fri, 3 Jan 2003 09:30:44 -0700 Subject: Fw: new JAXP 1.2 TCK compliant branch created (xml-commons todo's) To: commons-dev@xml.apache.org Cc: xalan-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: ilene@ca.ibm.com Date: Fri, 3 Jan 2003 11:26:56 -0500 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 5.0.9a |January 7, 2002) at 01/03/2003 11:26:59 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Shane wrote: > To-do's for Xalan include: updating the javax.xml.transform > code in the xml-commons tck-jaxp-1_2_0 branch with whatever > similar updates are needed; testing xml-xalan CVS with an > xml-apis.jar built from these sources; and if all's well, > asking for an xml-commons/./external release so that we can > checkin the static xml-apis.jar and related sources into > xml-xalan. I have updated the javax.xml.transform code in the xml-commons tck-jaxp-1_2_0 branch. It now contains the same code that was in the RIVERCOURT1 branch, plus a patch to StreamSource to use the same filename to URI conversion used by the javax.xml.parser package. Smoketest of xalan passes with an xml-apis.jar built from these sources. Shane wrote: > Note the xml-commons community will need to develop a > distribution structure for an 'external' release now > that xml-commons will be (unless someone disagrees) > shipping it's components separately (external/which/resolver > for now). Ilene. ---- on commons-dev@xml neilg@ca.ibm.com wrote ---- > I've created a new branch (tck-jaxp-1_2_0) containing code that's > JAXP 1.2 compliant and solves a number of bugs with code from > HEAD (especially having to do with security handling and robustness > with filenames containing characters such as spaces). I also > populated HEAD with this by mistake; sorry about that. :( I think > I've successfully reverted that error, but if someone could verify > that, I'd appreciate it greatly. > Note that I haven't updated the javax.xml.transform API on the > branch, nor the branch's manifest file; I thought I'd leave that to > the experts in such things. :)