You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transforming json keys directly to xml element names might e.g. also not work for arbitrary measurement names. These names are key (specification) and could be e.g. "min pressure" with blanks.
You could use a more verbose transformation like (net.sf.json.xml.XMLSerializer). So I think there's no need to adapt the time field nor would that alone help.
What's the objective of transforming json to xml in that case and not directly bind to your native implementation (c, python, etc.)?
Change request: please change the field name to something that can be used for a XML Binding too.
Thanks.
The text was updated successfully, but these errors were encountered: