eilly" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 16, 2003 9:04 PM
Subject: Re: DynamicConfigurator namespace problem
Stefan Bodewig wrote:
On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
elopers List" <[EMAIL PROTECTED]>
Sent: Tuesday, December 16, 2003 9:04 PM
Subject: Re: DynamicConfigurator namespace problem
Stefan Bodewig wrote:
On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
public class DynamicConfiguratorNS {
looks
Christopher Lenz wrote:
Am 16.12.2003 um 21:04 schrieb Peter Reilly:
The interface is:
public interface DynamicConfiguratorNS {
void setDynamicAttribute(String uri, String qualifiedName,
String value)
throws BuildException;
Object createDynamicElement(
Am 16.12.2003 um 21:04 schrieb Peter Reilly:
The interface is:
public interface DynamicConfiguratorNS {
void setDynamicAttribute(String uri, String qualifiedName,
String value)
throws BuildException;
Object createDynamicElement(
String uri, String
TED]>
Sent: Tuesday, December 16, 2003 9:04 PM
Subject: Re: DynamicConfigurator namespace problem
> Stefan Bodewig wrote:
>
> >On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >>public class DynamicConfiguratorNS {
&g
Stefan Bodewig wrote:
On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
public class DynamicConfiguratorNS {
looks fine to me.
I don't think this interface should extend DynamicConfigurator.
Same here.
I'd also like Ant to pass element and attribute names in as they a
Am 12.12.2003 um 15:40 schrieb Peter Reilly:
Christopher Lenz wrote:
Personally, I prefer DOM style as it is higher-level. The
qualifiedName parameter makes sense (well, sort of) when you can
enable/disable namespace support. When namespace support is always
enabled (as it is in Ant 1.6) the (na
Christopher Lenz wrote:
Am 12.12.2003 um 13:44 schrieb Peter Reilly:
Christopher Lenz wrote:
Same here. Proposed interface:
public class DynamicConfiguratorNS {
public Object createDynamicElement(
String namespaceURI,
String prefix,
String localName);
public void set
Am 12.12.2003 um 13:44 schrieb Peter Reilly:
Christopher Lenz wrote:
Same here. Proposed interface:
public class DynamicConfiguratorNS {
public Object createDynamicElement(
String namespaceURI,
String prefix,
String localName);
public void setDynamicAttribute(
Christopher Lenz wrote:
Am 12.12.2003 um 10:23 schrieb Stefan Bodewig:
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
Yes, either add DynamicConfiguratorNS or revert the change I made
yesterday to DynamicConfigurator.
I'm more inclined to add DynamicConfiguratorNS.
Same here. Propos
Jose Alberto Fernandez wrote:
From: Peter Reilly [mailto:[EMAIL PROTECTED]
Gurr..
In making the change to remove the "uri:" portion from
the DynamicConfigurator#createElement(String) (for elements
not in the ant core namespace uri), I forgot to check all
uses in ant 1.6.
This change breaks our
On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> But anyway, the DynamicConfiguratorNS interface I proposed doesn't
> help much for applications such as XSLT which make heavy use of
> namespace prefixes.
OK, it would have helped in the XMLFragement usecase.
> Maybe a NamespaceC
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
> Gurr..
>
> In making the change to remove the "uri:" portion from
> the DynamicConfigurator#createElement(String) (for elements
> not in the ant core namespace uri), I forgot to check all
> uses in ant 1.6.
>
> This change breaks our old frien
AM
Subject: Re: DynamicConfigurator namespace problem
Am 12.12.2003 um 10:23 schrieb Stefan Bodewig:
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
Yes, either add DynamicConfiguratorNS or revert the change I made
yesterday to DynamicConfigurator.
I'm more inclined to add Dynami
ss of the XML file writer, not the XML application. --DD
-Original Message-
From: Christopher Lenz
To: Ant Developers List
Sent: 12/12/2003 4:12 AM
Subject: Re: DynamicConfigurator namespace problem
Am 12.12.2003 um 10:23 schrieb Stefan Bodewig:
> On Fri, 12 Dec 2003, Peter Reilly
On Fri, 12 Dec 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
> public class DynamicConfiguratorNS {
looks fine to me.
> I don't think this interface should extend DynamicConfigurator.
Same here.
I'd also like Ant to pass element and attribute names in as they are,
i.e. without changing the
Am 12.12.2003 um 10:23 schrieb Stefan Bodewig:
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
Yes, either add DynamicConfiguratorNS or revert the change I made
yesterday to DynamicConfigurator.
I'm more inclined to add DynamicConfiguratorNS.
Same here. Proposed interface:
public class
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
> Yes, either add DynamicConfiguratorNS or revert the change I made
> yesterday to DynamicConfigurator.
I'm more inclined to add DynamicConfiguratorNS.
Stefan
-
To un
Stefan Bodewig wrote:
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
This change breaks our old friend which uses
DynamicConfigurator to implement elements and attributes of the
macros.
Does than mean that we'll need a DynamicConfiguratorNS in 1.6 to make
macrodef work? In o
On Fri, 12 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
> This change breaks our old friend which uses
> DynamicConfigurator to implement elements and attributes of the
> macros.
Does than mean that we'll need a DynamicConfiguratorNS in 1.6 to make
macrodef work? In order to avoid breaking
Gurr..
In making the change to remove the "uri:" portion from
the DynamicConfigurator#createElement(String) (for elements
not in the ant core namespace uri), I forgot to check all uses
in ant 1.6.
This change breaks our old friend which uses DynamicConfigurator
to implement elements and attributes
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
> One last thing to note; in ant 1.5 namespaces were not processed so
> x:y was passed tru without modification.
OK.
[example using a uri:local element snipped]
> This will not parse in ant 1.6,
exactly 8-)
So people realize that th
Christopher Lenz wrote:
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I
can't believe I'm the only one who has a problem with the current
implementation, which concatenates the namespace URI and the local
na
Am 11.12.2003 um 17:11 schrieb Peter Reilly:
One last thing to note;
in ant 1.5 namespaces were not processed so x:y was passed tru without
modification.
So the following:
Prints out:
Buildfile: dtest.xml
dtest:
[dtest] Element is uri:local
This will not parse in ant 1.6,
Stefan Bodewig wrote:
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
In ant 1.5, dynamicConfigurator#createElement(String) converted the
element name to a lower case
It still does for attributes, I've already been bitten by this 8-)
Should we keep this behaviour?
Proba
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
> In ant 1.5, dynamicConfigurator#createElement(String) converted the
> element name to a lower case
It still does for attributes, I've already been bitten by this 8-)
> Should we keep this behaviour?
Probably yes - and change the beh
Erik Hatcher wrote:
On Thursday, December 11, 2003, at 10:08 AM, Stefan Bodewig wrote:
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
I have no objection to passing just the localname if the other
commiters see no problem with this.
+1
If this means XDoclet won't break then a hearty
Stefan Bodewig wrote:
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
I have no objection to passing just the localname if the other
commiters see no problem with this.
+1
In ant 1.5, dynamicConfigurator#createElement(String) converted the
element name
to a lower case:
i.e.
On Thursday, December 11, 2003, at 10:08 AM, Stefan Bodewig wrote:
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
I have no objection to passing just the localname if the other
commiters see no problem with this.
+1
If this means XDoclet won't break then a hearty +1 as well.
Again, I
On Thu, 11 Dec 2003, Peter Reilly <[EMAIL PROTECTED]> wrote:
> I have no objection to passing just the localname if the other
> commiters see no problem with this.
+1
> - This will affect XMLFragment of cource.
XMLFragment is not part of Ant 1.6 and can easily be adapted to
whatever we decide f
Jose Alberto Fernandez wrote:
From: Christopher Lenz [mailto:[EMAIL PROTECTED]
Am 11.12.2003 um 14:49 schrieb Stefan Bodewig:
On Thu, 11 Dec 2003, Erik Hatcher
<[EMAIL PROTECTED]> wrote:
It's my own fault for not tracking this closer, so my
apologies for
coming i
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]
>
> Am 11.12.2003 um 14:49 schrieb Stefan Bodewig:
> > On Thu, 11 Dec 2003, Erik Hatcher
> <[EMAIL PROTECTED]> wrote:
> >> It's my own fault for not tracking this closer, so my
> apologies for
> >> coming into this late in the game. So, creat
Am 11.12.2003 um 14:49 schrieb Stefan Bodewig:
On Thu, 11 Dec 2003, Erik Hatcher <[EMAIL PROTECTED]> wrote:
It's my own fault for not tracking this closer, so my apologies for
coming into this late in the game. So, createDynamicElement now
receives more than it used to?! So it gets "uri:elementNa
Am 11.12.2003 um 13:44 schrieb Peter Reilly:
Christopher Lenz wrote:
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I
can't believe I'm the only one who has a problem with the current
implementation, which con
On Thu, 11 Dec 2003, Erik Hatcher <[EMAIL PROTECTED]> wrote:
> It's my own fault for not tracking this closer, so my apologies for
> coming into this late in the game. So, createDynamicElement now
> receives more than it used to?! So it gets "uri:elementName"?
... unless uri happens to be antli
On Thursday, December 11, 2003, at 07:44 AM, Peter Reilly wrote:
Christopher Lenz wrote:
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I
can't believe I'm the only one who has a problem with the current
impl
Christopher Lenz wrote:
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I
can't believe I'm the only one who has a problem with the current
implementation, which concatenates the namespace URI and the local
na
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I can't
believe I'm the only one who has a problem with the current
implementation, which concatenates the namespace URI and the local name
of the element to pas
38 matches
Mail list logo
