Hi Nick! ... *gasp* if you could see those happy-tears running from my eyes ;-)! This is nearly exactly what I thought of! Great, really - if I where a comitter: A BIG +1 for the functionallity :-) I tried it and it worked very well :-). I have to admit that i did not took a close look at your code (I'll do it now), but generally I am big fan of what you did!
Ok, Sim: please check out what he did and commit it if you do not have any concern ;-) *PLEASE* ;-). Again, Nick: Great work! Greatings, Chris > Hi, > > I really liked Chris' generic element idea... > > I created a prototype for the idea which uses > the ANT DTD to determine an element's possible > children. > > I hope you like it. > > Cheers, > Nick > > -- <Christoph Wilhelms> wrote: > > > > > > Well, I've got no question but I am still waiting > > > on your answer > > > regarding > > > FileSets implementation/Nested Feature > > > Implementation into Antidote... ;-) > > > I'd be happy to get to know your opinion of a > > > generic implementation for > > > nested elements like FileSet in general. BTW: I > > > took a look at > > > IntrospectionHelper ant I think it'll help us. > > > > > > -- <Simeon Fitch> wrote: > > > Until there is a common interface used by all tasks > > supporting fileset > > usage, I only see two options for Antidote: 1) Allow > > anything to have a > > fileset, and just assume the user knows what they're > > doing, 2) Provide > > ACSElement implementations and associated BeanInfo > > classes for those tasks > > that support properties of the "FileSet" type. > >
