We are using 2017 R3.
For some time now we have been consuming .NET Soap web services from one of our business partners. They now require us to migrate to a new web service technology, called RPC/JSON. This is outside negotiation.
I should like to have some advice on how to do this in the simplest way. With Soap, everything is generated in minutes and the serialization/des. is wholly automatic and all one has to think about is the content of the interface objects. These interface classes are pretty complex and deeply nested and so far they never fail unless the wsdl is ill-formed. We have a number of partners offering Soap web services.
The current plan is to use the httpclient object, and re-use all the interface classes from the Soap version. Next I think that I have to serialize/deserialize JSON back and forth between these and the httpclient object.
Is there a better overall strategy? If not,do I have to add serialization/des. methods to all interface classes, using the JSONGenerator/JSONParser objects or is there a simpler way? Any new features to expect in the next version of PB?
On the serialization side it looks more effective to make my own serialize-method for each interface object, with nested calls to similar methods in sub-objects (or arrays of sub objects) without using the generator object at all. On the return side the JSONparser object will provide some help in a similar fashion of nested method calls.
I'm putting together a presentation for DropBox API that uses their RPC endpoint. I'm planning to coordinate with Armeen about maybe doing a webcast for that, but either way I will post it on CodeXchange when I'm done. I will look for this post and add a link here when it's uploaded. Feel free to shoot me a message on LinkedIN if you need any outside assistance.