Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 57644 invoked from network); 10 Sep 2002 18:35:15 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Sep 2002 18:35:15 -0000 Received: (qmail 12792 invoked by uid 97); 10 Sep 2002 18:35:49 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 12739 invoked by uid 97); 10 Sep 2002 18:35:48 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 12721 invoked by uid 98); 10 Sep 2002 18:35:48 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <28336AC23B25D411BEA300105AC7F5441199A63B@ICEXCH2> From: "Shackelford, John-Mason" To: 'Ant Developers List' Subject: RE: handling external resources Date: Tue, 10 Sep 2002 13:35:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Erik, Ah, good thought. I want to leverage as much existing ant code as possible and that may be a way to do it. Is it an inappropriate use of a DataType to use it in a context where the DataType will never appear in a build.xml file? What I am doing (very left field :) ) is writing a framework that leverages the DynamicConfigurator and allows new tasks to be created via an XML task definition. The end user of the task will never see this XML file as it will just be jarred up with any auxilary classes required by the new task. It is this task definition I am concerned about reloading. In your judgement would creating a DataType to represent the task definition (which the end user never sees or knows about) be inappropriate? Thanks again, John-Mason Shackelford Software Developer NCS Pearson - Measurement Services 2510 North Dodge St. Iowa City, IA 52245 319-354-9200x6214 shacjo@ncs.com -----Original Message----- From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] Sent: Tuesday, September 10, 2002 1:24 PM To: Ant Developers List Subject: Re: handling external resources The word "reuse" triggers one thought: datatypes. Would that work in your situation? Erik Shackelford, John-Mason wrote: > I am working on a series of ant tasks each of which requires a > significant amount of external configuration via XML files. Since > parsing an XML file is somewhat expensive I thought that perhaps I > should keep the java rendering of that XML configuration around so > that when the task is run again the XML doesn't need to be reparsed. > Naturally I thought of creating a singleton repository for the > configuration info, but since Singletons have the reputation for being > evil I am wondering if there is a sanctioned Ant way of holding on to > external resources which may be reused and are expensive to acquire. > > > John-Mason Shackelford > > Software Developer > NCS Pearson - Measurement Services > 2510 North Dodge St. > Iowa City, IA 52245 > 319-354-9200x6214 > shacjo@ncs.com > > > ********************************************************************** > ****** > This email may contain confidential material. > If you were not an intended recipient, > Please notify the sender and delete all copies. > We may monitor email to and from our network. > **************************************************************************** > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > > > -- To unsubscribe, e-mail: For additional commands, e-mail: **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** -- To unsubscribe, e-mail: For additional commands, e-mail: