Re: Dealing with Trading Partners With Invalid JSON -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On Thu, Mar 28, 2024 at 10:17 AM Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>
wrote:

You can try with noxDb. It uses an object graph that will allow you to put
multiple nodes with the same name ( because noxDb also cater for XML where
this is natural)

Exactly what I thought... they just took their XML, converted it and that's
it. No validating, etc.

https://github.com/sitemule/noxDB

However it is a nasty job you got there from your boss. Why can’t you
convince the partner that’s wrong?

Well, I've been a consultant for this customer for years. Just a new
project we're working on and running into roadblocks like this.

We've done 100s of other projects without issue. This is with a new
trading partner, though. I honestly can say this is the first time I've
run into such horrible documentation, examples and the fact that the JSON
is invalid really takes the cake.

My only other option may be to just build the JSON by hand in a string or
IFS file... but I HATE doing things like that just to get around the
ignorance of another.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.