Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 49870 invoked by uid 500); 22 May 2003 15:28:23 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 49857 invoked from network); 22 May 2003 15:28:22 -0000 Message-ID: <3ECCEC8F.4070001@ieee.org> Date: Thu, 22 May 2003 11:28:15 -0400 From: James Black User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: axis-user@ws.apache.org Subject: Re: testing/debuggin best practices References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N John Klussy wrote: >I'm looking for information on how people are testing and debugging their web services. What tools are available out there. The two I've seen so far are XML Spy from altova.com and AppCanvas from canvassoft.com. Could anyone please recommend. > I do my development using Netbeans, and use the JUnit framework for unit testing. I test the server stubs separately, once they work, I then test the client side by having it go through the web service. -- "We do not lose our identity in our relations with others; in part, at least, we achieve our identity by those relations." Tony Blair, 1993