There is an example client written in VB that uses the ROPE proxy object, to call a 4S4C end point. ROPE requires a Service Description Language (SDL) file that describes the endpoint to call, there is a hand crafted SDL file http\asp\rope\services.xml that describes the Add function endpoint. Currently you need to write the SDL file yourself, or use the SDL Wizard that ships with the Microsoft SOAP toolkit.
Hopefully a future version of 4S4C will be able to dynamically generate the SDL for you, much like the ASP+ web services do in the Microsoft DotNet preview.
For those of you who have examined the XML generated by 4S4C, you will of noticed that it includes the <?xml version="1.0"?> tag that the ROPE proxy expects to find. (ROPE will fail if this is not included)
There are a number of examples included that use the Apache SOAP toolkit, also there is an AddressBook endpoint which should work with the addressbook sample included in Apache SOAP. All output elements are typed with a xsi:type attribute in order to work with Apache SOAP. The 4S4C UDT <-> Complex type mapping will work fine with the Apache Bean Serializer.
4S4C 1.2 will interop with Apache SOAP v2.0, it will not interop with earlier versions (including IBM SOAP 4J) because of incorrect namespace URI's for the xsd & xsi namespaces. However earlier versions of 4S4C, will inter-op with earlier versions of Apache SOAP, as they purposely emitted the wrong URI's as well.
There are two Perl examples that use the SOAP/Perl library from DevelopMentor. The two work well together where the feature sets match, however SOAP/Perl doesn't currently support Arrays, whilst it does support multi-ref accessors, which are not currently supported in 4S4C.
Microsoft's DotNet SOAP support, I'll also be doing some tests with this, although there won't be full interop until 4S4C supports multi-ref accessors.
Any other's you'd like to see here ?, if so drop me a note.