[EMAIL PROTECTED] wrote:
there are many ways to skin this catand I have done em all. I think we will
all wish in the near future that anything that consumes XML has such a default
ignore unknown xml handling, just makes life a little easier when
interoperating.
maybe, maybe not.
the or
"Jose Alberto Fernandez" <[EMAIL PROTECTED]> wrote ..
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> >
> > "Jose Alberto Fernandez" <[EMAIL PROTECTED]> wrote ..
> > > I do not see why we need to support this kind of thing.
> > > NO-one asks the javac compiler to be able to compile code in
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>
> "Jose Alberto Fernandez" <[EMAIL PROTECTED]> wrote ..
> > I do not see why we need to support this kind of thing.
> > NO-one asks the javac compiler to be able to compile code inside
your
> > Word document. If you have ANT inside some other m
On 9/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> "Jose Alberto Fernandez" <[EMAIL PROTECTED]> wrote ..
> > I do not see why we need to support this kind of thing.
> > NO-one asks the javac compiler to be able to compile code inside your
> > Word document. If you have ANT inside some other
"Jose Alberto Fernandez" <[EMAIL PROTECTED]> wrote ..
> I do not see why we need to support this kind of thing.
> NO-one asks the javac compiler to be able to compile code inside your
> Word document. If you have ANT inside some other markup, use an XSLT or
i think the larger the distance between
the do all for everything.
Jose Alberto
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 12 September 2005 13:44
> To: Ant Developers List
> Subject: Re: task namespaces
>
> Steve Loughran <[EMAIL PROTECTED]> wrote ..
> > I su
Steve Loughran <[EMAIL PROTECTED]> wrote ..
> I suppose there is nothing to stop us having a specific handler for
> unknown XML elements in targets or in project, with the default handler
> saying "this is unknown", but other configs handling it differently.
> Maybe it could be per-namespace inst
[EMAIL PROTECTED] wrote:
Steve Loughran <[EMAIL PROTECTED]> wrote ..
I have a build process that patches xsd files to deal with different
interpretations of the ##other namespace between xerces and .net. nobody
understands namespaces consistently.
yes and within the XML community the proble
Steve Loughran <[EMAIL PROTECTED]> wrote ..
> I have a build process that patches xsd files to deal with different
> interpretations of the ##other namespace between xerces and .net. nobody
> understands namespaces consistently.
yes and within the XML community the problems (with namespace interp
I guess an obvious question is what happens when something like this occurs:
...
Does the build fail?
-Rob
Steve Loughran wrote:
[EMAIL PROTECTED] wrote:
Robert Koberg <[EMAIL PROTECTED]> wrote ..
Peter Reilly wrote:
To allow easy use, the nested elements caused by java reflection o
Peter Reilly wrote:
To allow easy use, the nested elements caused by java reflection on
objects are placed in two namespaces - the default ant namespace (antlib:
org.apache.tools.ant)
and the namespace of the object that holds the nested element.
For example, the if task from ant-contrib extends
[EMAIL PROTECTED] wrote:
Robert Koberg <[EMAIL PROTECTED]> wrote ..
Peter Reilly wrote:
To allow easy use, the nested elements caused by java reflection on
objects are placed in two namespaces - the default ant namespace (antlib:
org.apache.tools.ant)
and the namespace of the object that hold
Robert Koberg <[EMAIL PROTECTED]> wrote ..
> Peter Reilly wrote:
> > To allow easy use, the nested elements caused by java reflection on
> > objects are placed in two namespaces - the default ant namespace (antlib:
> > org.apache.tools.ant)
> > and the namespace of the object that holds the nested
Peter Reilly wrote:
To allow easy use, the nested elements caused by java reflection on
objects are placed in two namespaces - the default ant namespace (antlib:
org.apache.tools.ant)
and the namespace of the object that holds the nested element.
This explains it, thanks - ignore my email that
[EMAIL PROTECTED] wrote:
Phil Weighill Smith <[EMAIL PROTECTED]> wrote ..
the only way those unprefixed elements are in some other namespace is if it is
declared at some encapsulating parent element.
for example;
http://www.example.org/someanturi";>
otherwise, if an xmlns declarat
To allow easy use, the nested elements caused by java reflection on
objects are placed in two namespaces - the default ant namespace (antlib:
org.apache.tools.ant)
and the namespace of the object that holds the nested element.
For example, the if task from ant-contrib extends ConditionBase, so
it
Phil Weighill Smith <[EMAIL PROTECTED]> wrote ..
> Jim,
>
> What you've said sounds wrong to me; and are in the
> "default namespace" (a declared namespace that has no prefix), whatever
> that has been defined to be.
which is why I said old chestnut...and responded in the way I did to make a
p
[EMAIL PROTECTED] wrote:
Steve Loughran <[EMAIL PROTECTED]> wrote ..
this action is a direct element; default NS or local
ns?
this is my new test, in the new ns
What confuses me here is that the ns of a nested element (not a type, an
element) is what? local? or Ant'
Jim,
What you've said sounds wrong to me; and are in the
"default namespace" (a declared namespace that has no prefix), whatever
that has been defined to be.
This could be the same as n1 if the URI for n1 is also associated with
the default namespace, but that seems unlikely.
Phil :n.
On Mon,
Steve Loughran <[EMAIL PROTECTED]> wrote ..
>
>
>
> I know separate namespace work is optional, but once you start on it it,
> it is more manageable. For this reason, the next edition of
> java-dev-with-ant will use namespaces everywhere too, except for the
> bits where I dont understand what
I know separate namespace work is optional, but once you start on it it,
it is more manageable. For this reason, the next edition of
java-dev-with-ant will use namespaces everywhere too, except for the
bits where I dont understand what is going on. Actually, I am slowly
building up model. N
21 matches
Mail list logo
