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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
The Wabbit
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
