On Wed, 5 Nov 2003, peter reilly <[EMAIL PROTECTED]> wrote: > On Wednesday 05 November 2003 16:26, Dominique Devienne wrote: >> > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] >> > >> > On Wed, 5 Nov 2003, Matt Benson <[EMAIL PROTECTED]> wrote: >> > > In beta1, the following worked: >> > > >> > > <myns:mytask> >> > > <myns:mytype /> >> > > </myns:mytask> >> > > >> > > In beta2, I get an error to the effect that "mytask" >> > > does not support nested "mytype". > > There was a bug in beta1 with regard to namespace > handling of nested elements (the prefix was > incorrectly ignored). > > This has been fixed in beta2.
See Matt, I told you it wasn't decided yet. Obviously Peter and I disagree on what the "correct" behavior would be 8-) > The current behaviour is that introspection discovered > nested elements belong to the ant default namespace. Why do you think it should do so? >> And what about an Ant task (say <dummy>) with a AddXyz(Xyz xyz) >> method, and I have an <my:xyz> in my AntLib that extends Xyz? >> Should I be able to say: >> >> <dummy> >> <my:xyz ... /> >> </dummy> > > No, the ant task needs to have a add(Xyz xyz) method for this to > work ... Peter is correct (of course, I should add). > well there is an undocumented attribute ant-type we really should document it. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
