----- Original Message ----- From: "Tom Jordahl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 04, 2002 7:14 AM Subject: RE: cvs commit: xml-axis/java/src/org/apache/axis/wsdl/toJava Jav aBeanHelperWriter.java SchemaUtils.java
> > Yes, yes, all well and good. I like tests too. +1 to that. But this is a document/literal .NET problem with an in/out parameter. > > We still have a serious problem including tests against a .NET service in our test suite. In fact we have a bit of a serious problem with any and all interop tests that aren't covered by the stuff Sam has set up. I am open to any and all suggestions as to how we can fix this. > I have posted a suggestion on how to do it for net client tests against Axis; have ant build files which get, import and compile WSDL descriptions; you could include code to test it. Ant does C# compilation on a win2K box, though without dependency checking. Because .net's wsdl tool doesnt generate Junit like test cases, there is a bit of work in writing test cases. > Can we get a .NET windows machines running somewhere in the apache.org domain that we can deploy custom test services on, then include the endpoints in our test suite? > How do you remotely manage a Win 2000 machine running .NET to deploy services? Can you do this? .net deployment is pretty much <copy>; <ftp> or <ftp> over SSH. Full system management is remote terminal services over SSH (perhaps to a nearby unix box), with the router set up to only deny remote terminal access from the outside. Or you get SSHD for NT from MKS, but not enough of the win2k tools run SSH to make it viable for all your management. You could do a test suite which has to get run locally, let individuals with their own private .net servers can test the stuff; run a gump and mail the failures; exclude that stuff out the junit tests unless dotnetserver.endpoint is defined -Steve
