Re: Dealing with Trading Partners With Invalid JSON

[Brad Stone <bvstone@xxxxxxxxx>]

LOL, Don.

You read my mind.  But you forgot the "well, if you think you know how to
do it, it's all yours...  contact me if you need help with future projects".



On Thu, Mar 28, 2024 at 5:44 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> After telling them they are wrong ... politely
>
> I would increase the price for the work you are doing - hopefully it is
> billable ?
>
> You have not said but is this a one way transaction - from you to the
> trading partner ?
>
> If yes, then as you have indicated it is like talking to a brick wall I
> would use RPG to build the string manually, with some clear comments
> indicating why and no swearwords!!.
>
> Cheers
>
> Don
>
>
>
>
> From:   "Brad Stone" <bvstone@xxxxxxxxx>
> To:     "Midrange Systems Technical Discussion"
> <midrange-l@xxxxxxxxxxxxxxxxxx>
> Date:   29/03/2024 01:08 AM
> Subject:        Dealing with Trading Partners With Invalid JSON
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
>
>
>
> Hello, all!
>
> How would you all deal with a trading partner that gives you specs on JSON
> for a web service where the JSON itself is invalid and the project
> manager just wants to work around it (bandaid style)?
>
> YAJL won't let me create the invalid JSON... the trading partner doesn't
> seem to care their JSON is invalid (I'd love to know what they're using to
> parse it... but because their docs are much more detailed on XML I would
> assume maybe they convert it from JSON to XML and then parse it).
>
> It's very frustrating to say the least.  Example:
>
> items {
>   item {....},
>   item {....}
> }
>
> Obviously the items object should be an array... YAJL won't let me create
> multiple item objects in (and it shouldn't..), the JSON fails the JSON
> validators... etc.. etc..
>
> When we ask for clarification they send another sample that has the same
> issues.
>
> Bradley V. Stone
> www.bvstools.com
> Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
> Cloud
> Provider!
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
>
>
>
>
> --
> This email has been scanned for computer viruses. Although MSD has taken
> reasonable precautions to ensure no viruses are present in this email, MSD
> cannot accept responsibility for any loss or damage arising from the use of
> this email or attachments..
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.