T
tbergman
Guest
Hi Bob, While there are likely many ways to deal with this, it may be simpler to think about this in terms of “send some text via HTTP”, “get back some text via HTTP”. Then do something with what you get back. This might mean forgetting about the libraries they provided. Possibly using their libraries with what you called “Raw Json” could also be considered. I’m not at all sure what their “JsonObject” is, it’s possible you could use that as well to parse your way through the Json. If there’s a way to test this service from a web browser, do that and examine the returned content. If not, try using a tool for REST (fiddler, SoapUI, probably others) and configuring the call. Or if you have a working sample from the vendor, sniff the conversation using Fiddler. Once you know the text being sent and received, and possibly a few things about the headers, you just have to figure out how to do this in Progress. I use the .Net WebClient or HttpClient to do this sort of thing. Then Progress or .Net tools for parsing the JSON/XML or whatever comes back. Parsing thorugh the Json and doing something with it is really not so different from parsing some csv and doing something. My .Net presentation from last year’s PugChallenge has a few examples of using WebClient, I know you know where to find it. Progress 11.6 has its own HttpClient capabilities (platform independent) but I haven’t spent any time with it. Tom
Continue reading...
Continue reading...