I'm in the process of working out how to commit the revised soap-gateway package that uses tDOM instead of ns_xml. It is a straight port of the original soap-gateway package.
I am further developing "service contract to web service" (sc2ws) support. Which means you are able to deploy a service contract implementation as a web service through a web interface.
The current method of deploying web services requires writing some procs in a library and importing it into soap-gateway. The sc2ws approach on the other hand means you don't have to write code if you want to interact with a package through web services. You just click a few check boxes, hit submit and a service contract implementation is then deployed as a web service.
An example of usage would be if you wanted to share your Learning objects in the LORSM package. sc2ws would allow you to deploy the "export learning objects" service contract implementation as a web service. This will allow LORSM to share learning objects with third party systems that also supports IMS standards. Well this is the vision I have for it.
As a result of this I have found that the soap-gateway package doesn't handle multiple return values very well, which is the case for the majority of service contracts. Also arrays aren't supported very well either. These are issues that I will be working on.