Comment 1:

This will be fixed as part of the encoding/xml cleanup (golang.org/s/go12xml).

Labels changed: added priority-later, go1.2, removed priority-triage.

Comment 2:

Status changed to Accepted.

Comment 3:

Labels changed: added feature.

Comment 4:

This issue was closed by revision 85f3acd.

Status changed to Fixed.

Comment 5:

This issue was closed by revision 56ce83f.

Comment 6:

This issue was closed by revision 54bdfc0.

Comment 7:

The code sample (http://play.golang.org/p/6lojzPMjov) that was not working well with xml
namespace, continue to *not* work even after the CL !

Comment 8:

Then there was no bug before. The generated XML is valid XML and is equivalent to yours.

Comment 9:

The bug is about:
xml with namespace --> Unmarshal into Go structure --> Marshal into xml
(output is valid xml but *without* namespace)
In the link I have provided, input:
<ns:mytag xmlns:ns="mynamespace">
    <Name>xyz</Name>
</ns:mytag>
output:
<mytag xmlns="mynamespace">
        <Name>xyz</Name>
</mytag>
Isn't this an issue?

Comment 10:

If I provide the input as:
    <ns1:mytag xmlns:ns1="http://www.mynsdefs.org/nsdefs-here-ns1">
    <ns2:Name>xyz</ns2:Name>
    </ns1:mytag>
Output is:
    <mytag xmlns="http://www.mynsdefs.org/nsdefs-here-ns1">
        <Name>xyz</Name>
    </mytag>
Isn't this an issue?
ns1 & ns2 are gone in the output. play link: http://play.golang.org/p/7V9gprqiG-

Comment 11:

I was hoping to use it for soap :)