[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.wsvt] Re: Call to participate in the design and implementation of a SOAP Message Monitor and Debugger
Thanks for the note Peter. I will definitely checkout the SOAP monitor included in Axis. I hope once we have fleshed out a concrete design that we can get further comments from you.
Thanks.
-- David
"Peter Chilcott" <tedbear84@xxxxxxxxxxx> wrote in message news:bnoe3e$877$1@xxxxxxxxxxx...
Hi,
The base TCPMon can resend a message as I recollect.
A SOAP Monitor that would only catch messages that met certain criteria would be interesting. Particulariuly if these included HTTP Header variables, SOAP header fields and IP addresses/hostnames. User definable actions might be a good idea as well. Something like the different log4j apenders, ie. log2file, log2screen, log2email with sub portions of the message.
 
Cheers.
"David Lauzon" <lauzond@xxxxxxxxxx> wrote in message news:bnbj8r$vjv$1@xxxxxxxxxxx...

The Eclipse project, WSVT (Web Service Validation Tools), is starting work on a SOAP Message Monitor and Debugger. We have begun fleshing out the requirements and have an initial draft. We are now looking for feedback, comments or contributions. The document is located on our project website, WSVT, or you can directly access it here.

We are looking to design and implement a SOAP Message Monitor and Debugger that can serve both as a testing tool for web services during development and as a diagnostic tool for web services during deployment. Among other things, the tool should include the following features:

  1. the ability to resend messages already captured.
  2. the ability to set break points on:
    • a message (which could be used by more than one operation);
    • an operation;
    • a binding (i.e., any message for any operation in the binding) and
    • a port (i.e., any message for a specific endpoint).

Volunteers? Any feedback, comments or contributions?

Thanks.

David Lauzon.