In the Java project we already have some interop tests in tuscany/java/testing/interop/ so for these SDO ones how about tuscany/java/testing/interop/sdo?
How about a mix for options (2) and (3) - I can understand duplicating the resources across Apache and PECL, but at least within Apache Tuscany could all the language impls share a common resource folder, maybe tuscany/interop/resources? Note I don't really mind so if either of these suggestions make things more difficult I'm fine with the suggestions in your email. ...ant On 6/19/06, Simon Laws <[EMAIL PROTECTED]> wrote:
I've done more work on this. The issues that have been raised so far Java None raised so far C++ JIRA444 - Causes crash JIRA445 JIRA447 JIRA448 - Causes crash - Pete has fixed JIRA449 JIRA450 JIRA451 JIRA452 JIRA453 Off the two that cause runtime crashes 444 remains unresolved. The others lead to output that doesn't match the input. PHP As C++ (as it is based on C++) plus PECL7878 PECL7879 PECL7880 Of these 7878 and 7879 as usability issues. I'm going to take a look a 7880 There is still more testing to do, particularly around Axis2 between Java and C++, but most things have been working so far so my confidence levels are building. From my previous mail on this subject I'm still undecided about where to put the code. There is not much code involved but it needs to live somewhere. I've been assuming to date that the test code will happily live within each project somewhere (where is a good place in each project structure?), for example, it could be Java: tuscany/java/sdo/impl/src/test/org/apache/Tuscany/sdo/interop C++: tuscany/cpp/sdo/runtime/core/interop PHP: tuscanyphp/sdo-1.0.1/tests/interop The input files (XSD, XML, DDL etc) themselves are common across all projects. So where should they live? 1/ Just pick on project, C++/Java/PHP, and put the common files there. You have to check the files out and move them around to set up for testing 2/ Duplicate the common files across all projects. Leads to maintenance problem but is convenient for running the tests 3/ Create some common interop directory somewhere. Don't know where this would be As the projects are spread across Apache and PECL I would go for option 2 and suffer the maintenance burden. I.e. to test PHP I don't really want to ask the developer to go and retrieve files from Apache. Thoughts? Simon
