While it's certainly a great thing to be able to set up local .NET tests, I added a "playback" handler today which can fill the role of the server for simple "one-roundtrip" tests, simulating whatever response we desire. I'd like to filter the tests into "simple" and "complex" ones, where the "simple" ones are those which can just use the playback feature to check how we deal with receiving particular messages - we can integrate these into our functional tests very easily. The "complex" ones require actual code running on .NET.
--Glen > -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 14, 2002 9:09 PM > To: axis-dev > Subject: dotnet local tests > > > I'm putting together the tests for axis client against a > local .net server; > expect the commits to come in this week. > > If you want to run these, install IIS and then .NET framework > 1.0. you wont > need vs.net; just the framework installed *after* you install > IIS. Oh, and > dont forget the security patches for IIS. > > How many people will be able to do this? IIS is the > showstopper; we may want > to think about adding support for cassini > (http://www.asp.net/Projects/Cassini/Download/) (think jetty > for ASP.net), > but I dont want to add complexity (or an unrealistic server). > > once the process is in place we can start adding more bugreps to the > endpoints; for .net bugs from now on we should start asking > for the endpoint > code snippets too. > > -Steve >
