Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 86465 invoked from network); 15 Jun 2000 01:42:41 -0000 Received: from e22.nc.us.ibm.com (32.97.136.228) by locus.apache.org with SMTP; 15 Jun 2000 01:42:41 -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 VAA16238 for ; Wed, 14 Jun 2000 21:21:43 -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.9) with SMTP id VAA29504 for ; Wed, 14 Jun 2000 21:42:40 -0400 Received: by d54mta04.raleigh.ibm.com(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 852568FF.000964BE ; Wed, 14 Jun 2000 21:42:36 -0400 X-Lotus-FromDomain: IBMUS To: ant-dev@jakarta.apache.org Message-ID: <852568FF.0009628C.00@d54mta04.raleigh.ibm.com> Date: Wed, 14 Jun 2000 21:41:10 -0400 Subject: RE: [RFE] Richer Task Specification 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 Peter Donald wrote: > But scripting should prolly deal with the XML tree > rather than directly with objects so you are not tied > to any particular implementation ??? A second reason is that there is no XML tree. The parser is SAX, which simply fires off events as it is reading the file. The way this currently works is that when the following is read: This results in a creation of an actionTask object, then a call to setFoo("bar") on that object, then a call to init(). So for the circumstances where the object can't be created yet, instead of calling setFoo("bar"), the name of the attribute and value must be stashed away somewhere and processed later. - Sam Ruby