On 11/13/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
Hi Dan, The C++ interop test service I added is at http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/test/ws.service.interop/ This can be run on Linux via "make check" (after it's been built) or on Windows via the ws.service.interop.client/runclient.bat file - this uses the 50-odd SDO interop schemas copied from http://svn.apache.org/repos/asf/incubator/tuscany/interop/ and exposes each one as a web service operation, implemented by a C++ class. Each class method takes a DataObject, compares it with one loaded from some XML on the file system and returns it back to the client (where it is also compared with the original from the file system). See the following thread for more info: http://www.mail-archive.com/[email protected]/msg08385.html Hope that's useful - I'm happy to help improve/expand on this Cheers Andy On 11/13/06, Dan Murphy <[EMAIL PROTECTED]> wrote: > Hi Simon, > Interop testing with PHP, C++, etc was certainly one of the things I was > thinking of... > The way I see it is that the tests could be run in a number of different > modes: > > serialiseSDOs - serialise SDO object to file system so they could be loaded > by different impl > deserialiseSDOs - load SDO objects from serialised > useDynamicSDOs - programatically generate SDO using APIs > useGeneratedSDOs - generate SDOs from schema and use the generated ones to > run tests > > I see serialise/deserialise option used to test interop between different > implementations of SDO - esp interop between implimentation languages. The > useGeneratedSDOs only makes sense with Java implementations (as I understand > it Java is the only one to generate simple objects to represent SDOs). > > All the tests would need to cover the features descriped in the spec (or > agreed subset), for the serialise/deserialise tests to work there would need > to be shared SDO descriptions used - eg. C++ serialises a "customer" and > Java deserialises it and checks the SDO is as expected). > > I'd be happy to work on the Java side, my C++ is rather poor so together I > think we could make some progress together - if the interop is needed... as > you say, would be a poor show if (complex) C++ serialised SDOs couldn't be > read by the Java impl... > > Cheers, > Dan > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Dan
Sounds like we are singing from the same hymn sheet as they say. We have concentrated on the serialize/deserialize SDOs for the cross language interop work we have done to date. This is the natural mode of operation when passing an SDO, i.e. it is serialized at one end and deserialised at the other. From Andy's descripition you can see how SDOs are bounced back and forth and compared with one another. What we need is a Java version of the same service so we can have java play opposite itself and C++ as both client and server. We should look at dynamic SDOs too (for the sample schemas?) but we haven't got round to that yet. We tried to summarize the various tests that need running in the README.txtassoicated with the interop test cases ( https://svn.apache.org/repos/asf/incubator/tuscany/interop/src/main/resources/README.txt). This could well do with a bit of review and updating now. Might be a good place to start. Regards Simon
