Hi Guys, I stack in a strange issue regarding convert JSON to XML in node-red v1.0.3. I have a code where I composing the specified XML for 3rd party server endpoint communication. The structure need to consist special characters like equation = In the past it worked well to convert this JSON to X…

The xml node should work both ways. So a good way is to feed in the xml you want then see what json comes out. And then make you json look like that.

[image] roleeka: "<?xml version="1.0" encoding="UTF-8" standalone="yes"?><foo=>bar</foo=> Are you sure that is valid XML? Try feeding it into an XML validator to check.

I’m not sure wether is valid or not but the structure of the XML is defined with the 3rd party endpoint. What I could manage to installed xml-js package and add to require this into node-red settings.js and use this idirectly from function node instead of built in xml node. Now it works, but what c…

As @colin said - it isn't valid xml. I'd be very wary of any API that claimed that it was. Are you sure that they really think it is ?

It's academic if it's valid XML or not. If it is the format the remote API requires then that is what is needed. @roleeka between 1.0.0 and 1.0.3 the xml2js module we use was upgraded from version 0.4.19 to 0.4.22. So I would not have expected a breaking change to have occurred. I guess the face it…

If the older one allowed invalid XML to be generated that would be a bug fix. The improved validation of data will only break code that shouldn't have worked in the first place. I don't think that would normally be considered a breaking change.

This url will show you all of the commits between the 2 versions. [image] Leonidas-from-XIV/node-xml2js XML to JavaScript object converter. Contribute to Leonidas-from-XIV/node-xml2js development by creating an account on GitHub.

Thanks the info, I had the same guess and agree to move into standard direction, but many cases you have to implement what you get as a specification and if the spec is non standard you have difficulties. I think, we can close this topic, thanks the fast answers and luckily node-red flexible enough…

Node-RED

Node-RED Forum

V1.0.3 XML node Error: Invalid character in name

General

Colin 15 February 2020 07:26 3

Are you sure that is valid XML? Try feeding it into an XML validator to check.

Topic		Replies	Views
XML-node XML->JSON Error: Invalid character in name General	19	2099	6 July 2021
Invalid Character in Name General	10	1717	9 April 2020
Special character encoding /Utf8 problem General	9	6709	22 November 2018
Trouble converting XML General	2	334	17 August 2022
JSON to XML correct syntax General	7	206	6 November 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

V1.0.3 XML node Error: Invalid character in name

Related topics