I don't believe that's changed. If memory serves (it's a long time since
I looked at this), the below is an artifact of whatever library is used
to dump out the XML. I'm going to look at some XMLTask work next week,
so I will put this on my list of issues to (at least) investigate.
Can you confirm whether this happens if you disable any outputter
definition in your XMLTask - i.e. use the default ? And can you send me
a cut down version of your XML that demonstrates this behaviour ?
Brian
On 24/7/09 15:14, Holger Rauch wrote:
Hi,
is the problem described in
http://osdir.com/ml/java.ant.xmltask/2008-04/msg00008.html
still current? Reason why I'm asking:
I too got the problem that xmltask "decides" to introduce some kind of
artificial default namespace prefix like e.g. __NS1 upon<insert>s
and/or<replace>s that are *not* present in the original, unmodified
version of the corresponding XML file.
So, I get newly inserted XML elements like this:
<jar-name __NS1:xmlns="" xmlns="">...</jar-name>
even though I want them simply to read
<jar-name>...</jar-name>
Can I suppress the generation of this prefix somehow?
Thanks in advance for any info!
Kind regards,
Holger
------------------------------------------------------------------------
------------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________
Xmltask-users mailing list
Xmltask-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xmltask-users
--
Brian Agnew http://www.oopsconsultancy.com
OOPS Consultancy Ltd
Tel: +44 (0)7720 397526
Fax: +44 (0)20 8682 0012
------------------------------------------------------------------------------
_______________________________________________
Xmltask-users mailing list
Xmltask-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xmltask-users
