You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Wascally Wabbit <wa...@earthling.net> on 2004/05/19 00:19:33 UTC
Is DynamicConfigurate slated to be made namespace-aware?
Hi All,
Just wondering if DynamicConfigurator's "createDynamicElement"
will be supplemented for namespace-bound elements? Perhaps a
new interface that extends DynamicConfigurator? Currently I
cannot get the full context for the element so "a:thing" is
passed in as "thing"...which ComponentHelper cannot find.
The Wabbit
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Is DynamicConfigurate slated to be made namespace-aware?
Posted by Wascally Wabbit <wa...@earthling.net>.
Much Thanks,
I've recorded this as part of my "To Do" list for next Ant release.
At 10:02 AM 5/19/2004, you wrote:
>Wascally Wabbit wrote:
>
>>At 04:06 AM 5/19/2004, you wrote:
>>
>>>DynamicConfigurator is NS unaware.
>>>(This was for BC reasons, in ant1.6betaX).
>>>
>>>There is work in progress to make
>>>a DynamicConfiguratorNS -
>>>see:
>>>http://issues.apache.org/bugzilla/show_bug.cgi?id=28426
>>>
>>>One question:
>>>should the interface give the ns prefix or the qualified name,
>>>ie:
>>> Object createDynamicElement(
>>> String uri, String prefix, String localName) throws BuildException;
>>>
>>>or
>>>
>>> Object createDynamicElement(
>>> String uri, String qualifiedName, String localName) throws
>>> BuildException;
>>>
>>>The second form may be more useful for talking to Dom.
>>>
>>>Peter
>>
>>
>>
>>I think the second form can also be passed directly into
>>ComponentHelper's various APIs without a side call to
>>'genComponentName'. So the second form gets my vote...
>>
>This is not unfortunately correct.
>The component name has the "uri" and not the ns prefix,
>so one would still need to do genComponentName(uri, localName)
>
>Peter
The Wabbit
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Is DynamicConfigurate slated to be made namespace-aware?
Posted by Peter Reilly <pe...@corvil.com>.
Wascally Wabbit wrote:
> At 04:06 AM 5/19/2004, you wrote:
>
>> DynamicConfigurator is NS unaware.
>> (This was for BC reasons, in ant1.6betaX).
>>
>> There is work in progress to make
>> a DynamicConfiguratorNS -
>> see:
>> http://issues.apache.org/bugzilla/show_bug.cgi?id=28426
>>
>> One question:
>> should the interface give the ns prefix or the qualified name,
>> ie:
>> Object createDynamicElement(
>> String uri, String prefix, String localName) throws
>> BuildException;
>>
>> or
>>
>> Object createDynamicElement(
>> String uri, String qualifiedName, String localName) throws
>> BuildException;
>>
>> The second form may be more useful for talking to Dom.
>>
>> Peter
>
>
>
> I think the second form can also be passed directly into
> ComponentHelper's various APIs without a side call to
> 'genComponentName'. So the second form gets my vote...
>
>
This is not unfortunately correct.
The component name has the "uri" and not the ns prefix,
so one would still need to do genComponentName(uri, localName)
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Is DynamicConfigurate slated to be made namespace-aware?
Posted by Wascally Wabbit <wa...@earthling.net>.
At 04:06 AM 5/19/2004, you wrote:
>DynamicConfigurator is NS unaware.
>(This was for BC reasons, in ant1.6betaX).
>
>There is work in progress to make
>a DynamicConfiguratorNS -
>see:
>http://issues.apache.org/bugzilla/show_bug.cgi?id=28426
>
>One question:
>should the interface give the ns prefix or the qualified name,
>ie:
> Object createDynamicElement(
> String uri, String prefix, String localName) throws BuildException;
>
>or
>
> Object createDynamicElement(
> String uri, String qualifiedName, String localName) throws
> BuildException;
>
>The second form may be more useful for talking to Dom.
>
>Peter
I think the second form can also be passed directly into
ComponentHelper's various APIs without a side call to
'genComponentName'. So the second form gets my vote...
>Wascally Wabbit wrote:
>
>>Hi All,
>>
>>Just wondering if DynamicConfigurator's "createDynamicElement"
>>will be supplemented for namespace-bound elements? Perhaps a
>>new interface that extends DynamicConfigurator? Currently I
>>cannot get the full context for the element so "a:thing" is
>>passed in as "thing"...which ComponentHelper cannot find.
>>
>>
>>The Wabbit
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
The Wabbit
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Is DynamicConfigurate slated to be made namespace-aware?
Posted by Peter Reilly <pe...@corvil.com>.
DynamicConfigurator is NS unaware.
(This was for BC reasons, in ant1.6betaX).
There is work in progress to make
a DynamicConfiguratorNS -
see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=28426
One question:
should the interface give the ns prefix or the qualified name,
ie:
Object createDynamicElement(
String uri, String prefix, String localName) throws BuildException;
or
Object createDynamicElement(
String uri, String qualifiedName, String localName) throws
BuildException;
The second form may be more useful for talking to Dom.
Peter
Wascally Wabbit wrote:
> Hi All,
>
> Just wondering if DynamicConfigurator's "createDynamicElement"
> will be supplemented for namespace-bound elements? Perhaps a
> new interface that extends DynamicConfigurator? Currently I
> cannot get the full context for the element so "a:thing" is
> passed in as "thing"...which ComponentHelper cannot find.
>
>
> The Wabbit
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org