I think that Peter Donald effectively solved/ended this thread earlier today. The concept that multiple inputs to taskdefs combined in one input string should be avoided when unnecessary is a good design guideline to follow.
Tim O'Brien [EMAIL PROTECTED] -----Original Message----- From: Tom Dimock [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 28, 2000 12:49 PM To: [EMAIL PROTECTED] Subject: RE: proposing TaskUtil.java At 11:31 AM 06/28/2000 -0400, Tim wrote: >What would you prefer: > ><available classname="org.whatever.MyClass,org.whatever.MyClass2" >property="myclasses.present" >/> Ugly, becomes very difficult to read if the list gets very long. ><available property="myclasses.present"> > <resource classname="org.whatever.MyClass"\> > <resource classname="org.whatever.MyClass2"\> ></available> Much more readable. Should the inner tag be <resource classname="whatever"/> or <class name="whatever"/>? The latter would seem to allow for fairly straightforward extension to other resource types. Or maybe <available property="myclasses.present"> <resource.class name="org.whatever.MyClass"\> <resource.class name="org.whatever.MyClass2"\> </available> which retains the extensibility, but still makes it clear that this is a resoucre check... ---------------------------------------------------------------------------- Tom Dimock ---- Cornell University ---- [EMAIL PROTECTED] "There go my people. I must follow them, for I am their leader." M. Gandhi
