On Wed, 25 Jul 2001, Conor MacNeill <[EMAIL PROTECTED]> wrote: > From: "Stefan Bodewig" <[EMAIL PROTECTED]>
>> What problems do you see with allowing arbitrary other child >> elements as well? > > I was worried about the impact on the use of UnknownElements. I see. > There is no loss of capability as nested elements can themselves be > TaskContainers. So, you can have a list of tasks in one nested > element and other nested elements for other things I can live with that - it might make some tasks look a little silly, but that's OK. > I see now, however, that you will not be able to taskdef > TaskContainer Tasks since the UnknownElement will not be a > TaskContainer. I guess RuntimeConfigurable.maybeConfigure will pick > up the task container. I'll give it a second look. Stefan
