On Monday 05 May 2003 20:20, J.Pietschmann wrote:
> peter reilly wrote:
> > I would agree with most of what Nicola says. I think
> > that XML ns is a "heavy" solution for name clashing
> > of names defined in a antlib. Moreover I do not
> > think that the antlib needs to define a qualified name.
>
peter reilly wrote:
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be used - even with the
peter reilly wrote, On 04/05/2003 2.03:
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be
>
> Costin Manolache wrote, On 03/05/2003 8.22:
> ...
> > One use case I had in mind for CH was a namespace like "jmx:...",
> > where the JMXComponentHelper would use the JMX metadata to
> create the
> > task ( no ant table ). That's clearly outside the scope of
> antlib or ant (
> > it's just
I would agree with most of what Nicola says. I think
that XML ns is a "heavy" solution for name clashing
of names defined in a antlib. Moreover I do not
think that the antlib needs to define a qualified name.
The "prefix" attribute idea of the task could
be used - even with the current command.
Costin Manolache wrote, On 03/05/2003 16.14:
Nicola Ken Barozzi wrote:
...
I think that XML namespaces really make things much more difficult to
write and understand. One thing I don't like in Jelly is just this use
of namespaces, where all scripts seem cluttered and simply difficult to
read.
I ag
Nicola Ken Barozzi wrote:
This seems interestig, and brings up what XML namespaces can be used for.
XML namespaces are indented to disambiguate short local element
and attribute names. Any sematic associated to XML namespaces
beside this has to be weighted carefully.
Lets take an example. There are
Nicola Ken Barozzi wrote:
>
> Costin Manolache wrote, On 03/05/2003 8.22:
> ...
>> One use case I had in mind for CH was a namespace like "jmx:...",
>> where the JMXComponentHelper would use the JMX metadata to create the
>> task ( no ant table ). That's clearly outside the scope of antlib or ant
