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 [EMAIL PROTECTED] **************************************************************************** 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
