escaping comments in xml

[harrycaul]

I apolgize if this has been fixed already, as we are using Vault 1.1.2 (with plans to upgrade soon). But I can't find any reference to it.

I'm in the process of using CruiseControl.NET for automated builds. It works by grabbing the history XML from Vault and parsing it. Problem is a comment in an old checkin has an accidental "<" in it, which isn't escaped in the XML document, which is illegal syntax.

Vault should properly escape those characters in the resulting XML. Alternatively, it'd be nice to have an option to return history information without comments (saves bandwidth).

If you're interested, I'm getting around this now by having CruiseControl return only the top 100 rows of the history, instead of all of them.

[jclausius]

harrycaul:

Thanks for the report. The Command Line client only provides XML-like output, not XML.

There is a logged feature request to use standard XML.

[bradm]

We are having a message that states the xml document (1,583) has an error of 'Element' is an invalid node type 1, position 583.

Is this related to the history xml document. and if so, how can we fix this. It has locked all the developers out of working on the solution.

[dan]

We'll need more details on what the problem is. Which version of Vault are you using, and is this part of integration with a build tool?

[jeremy_sg]

Brad's problem is not related to the CLC. He's emailed goldsupport, and we're dealing with his issue offline.