On Wednesday 17 September 2003 12:59, Stefan Bodewig wrote: > On Wed, 17 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote: > > The <c:define.with.echo> element gets rejected in > > UnknownElement#handleChildren() before > > Antlib#addConfigured() is called for the <presetdef> element > > of the antlib. > > I see. It seems we have a certain class of tasks with "what can be > nested into the task depends on what has been nested into it before". > <sequential> was the first with that problem and we fixed it by > special casing TaskContainer. > > The way TaskContainer is treated here has always been a hack - well, > most of the UnknownElement/RuntimeConfigurable combo is ;-) - and it > sure felt better if we'd have a clean way to signal that an object > needs to defer child creation. I now understand why you went the > Taskcontaier route and would be OK with rejecting non AntlibInterface > instances for now.
Ok I have modified Antlib.java to reject non AntlibInterface task instances, will deal with types tomorrow. Peter > > The alternative might by DynamicConfigurator which itself could defer > the child creation. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
