KDSoap
KDSoap copied to clipboard
KDAB
WS-* Support
I'm trying to figure out which WS-* specifications the library support but I can't find this information anywhere?
What is the current WS-* specification support status? The only information I could find was that SOAP 1.2 support is coming soon. Also which is the WS-I Basic Profile version supported by the library?
These are additional specifications on top of SOAP 1.1/1.2? I only know about WS-Security, which is not implemented by KDSoap at the moment. Which other specs did you have in mind?
These are advanced web service specifications you can see a list of the existent ones over here http://en.wikipedia.org/wiki/List_of_web_service_specifications.
I was checking the availability of support in the library of WS-Security, WS-Addressing, WS-ReliableMessaging and WS-Discovery. Most toolkits support at least the first three WS specifications.
I had a patch (not totaly done tho) for a implementation of WS-Adressing, but I lost most of it when my HD crashes, some months back. I could make it again ( quicker than before ). But I need some days to do so.
Would just like to comment that my company would be interested in seeing official WS-A support in KDSoap. We are currently using KDSoap with our own bolted on WS-A support.
While I doubt it helps much, @dfaure-kdab got a patch with what we had done 2014-02-25
I will have some days this month, I'll work on WS-Adresing to get it as done as possible :) @chrols : Yeah, I had a look at it when I started my patches, did help me to grasp the spec easier.
I will keep my progression updated here I guess :)
We pushed a client side support for WS-Addresing, usable from this commit : 8cfe017471adcc37a0ee6b23a87c701a811b09ec
I was wondering if there are any further plans on implementing WS-Security? I'm currently looking into making them myself within kdSOAP, but I'm having trouble setting up the headers with the proper indents (Security->UsernameToken->Username). Is this perhaps something that you have already been working on, and if not, is it something that is on the roadmap?
This is not currently planned, but maybe this is something you can contribute, either in form of a patch, or in form of funding the implementation by KDAB?
