ksoap2-android meets okhttp

The ksoap2-android project has been in mostly maintenance mode for a long time, but it is still receiving lots of usage. Recently a very useful improvement came up in discussions around HTTP connections issues. The robust and powerful OKHttp library can be used to create an alternative transport. With the new 3.6.1 release I just created recently, you now have access to transport and service connection classes that use the latest OKHttp release. This will make your SOAP service connection more reliable across devices.

And it will also allow us to improve this even further – so what are you waiting for. Send me your own improvements.

2 comments » Write a comment

  1. Hello,

    So OkHttp is now used by default or it requires some configuration for a client first? How to set the client to be OkHttp?

  2. Hello,

    Currently, version 3.6.2 of ksoap2-android is compiled with OkHttp version 3.2. There is an open topic on the github site (issue #108) talking about possibly updating ksoap2-android to use OkHttp 3.6 or greater. Is this still being considered? I asked because I have a similar issue using another networking library that uses OkHttp 3.6 and the different dependency causes a Java Verify Error when using a OkHttp client with ksoap2.

Leave a Reply

Required fields are marked *.