Hi all

I've mentioned to a couple of you that I'm going to create
an interoperability testbed. I'd like to get some feedback
from this group.

For each if a number of different SOAP implemenation, I'm
planning to host a service that exposes these methods

String echoString(String inputString)
String[] echoStringArrray(String[] inputStringArray)
Integer echoInteger(Integer inputInteger)
Integer[] echoIntegerArray(Integer[] inputIntegerArray)
Float echoFloat(Float inputFloat)
Float[] echoFloatArray(Float[] inputFloatArray)
SOAPStruct echoStruct( SOAPStruct inputStruct)
SOAPStruct[] echoStructArray (SOAPStruct[] inputStructArray)

Where SOAPStruct is a simple structure with integer, float, and
string fields.

Other possibilities include:
Hashmap / Associative array , using the encoding proposed by
the Apache folks.
XML Documents

This "echo" service does nothing really useful except
illustrate the ability of the service to accept a clients
envelope, deserialize the types correctly, and then
reserialize the respones into something that the client
can see if it understands.

I built this service for Apache 2.0 and SOAP::Lite a few
months ago, and I think Paul Kulchenko will agree that
it's been really useful for testing interop issues.


In addition to exposing these services, I also plan to:

* Publish wiredumps of the request and response envelopes
that each implementation uses - ie, each implementations
client
* For those implementations that dynamically generate
WSDL, I will publish the WSDL generated for each of these
methods.

I think this is a first step to REALLY filling out those issues
lists for SOAP and WSDL interoperability. It's much easier to
see the issues when all this info is right in front of you.

My question here is :

Does this set of types/methods make sense? Would you modify
this list in any way?

Thanks for any feedback!

Tony

----------------------------------------
XMethods Web Services Listings
http://www.xmethods.net