----- Original Message ----- From: "Glen Daniels" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 04, 2002 7:48 AM Subject: RE: cvs commit: xml-axis/java/src/javax/xml/rpc/soap SOAPFault.ja va SOAPHeaderFault.java
> +1 to all of that. I think we should have most of our tests/samples be Axis-specific, and then have a "JAX-RPC compliance" section in both the samples and the tests. Code review of samples and, even more pressingly, tests, would be really great. I'm going to jot in by an observation that as a producer/consumer of web services, a lot of my problems are becoming 'can C# import and compile my service'; 'can wsdl2java generate code from my service's WSDL that compiles'? I dont see any tests for that in Axis yet. It is not hard to add these tests, because each test can be described in a single Ant build file (of, course, you need the .NET framework to run the C# tasks). I stuck an example of a build file to demonstrate a bug as an attachment to a (now fixed) WSDL bug a couple of weeks ago. What you do need to do is steal the Junit Testcase extension class, org.apache.tools.ant.BuildFileTest from src/testcases in ant, and write subclassed test case classes, one per build file, with each test method running a single target in their build file. If you want to adopt this test mechanism for integration tests, I can get you started with a sample test build file/test class or two. You'd need to duplicate the BuildFileTest class in your own source tree; it aint include in ant distributions to avoid having to keep its behaviour consistent from week to week. -steve
