ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <jakarta-...@ehatchersolutions.com>
Subject Re: handling external resources
Date Tue, 10 Sep 2002 20:32:07 GMT
You're doing some wacky stuff, so its hard for me to comment!  :)

I think you'll have to use your best judgement on how to do this - but 
you could still set a project-scoped datatype from within your task that 
later tasks could see, and the user would never see an actual datatype 
declaration.

	Erik


Shackelford, John-Mason wrote:
> 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:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
>>For additional commands, e-mail: 
>><mailto:ant-dev-help@jakarta.apache.org>
>>
>>
>>
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
> 
> **************************************************************************** 
> 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:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
> 
> 
> 



--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message