axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Davis" <>
Subject Re: tcpmon improvements
Date Fri, 02 Nov 2001 18:45:23 GMT
Maybe but then you have to know where to get the right data - for example,
we look at the URL, SOAPAction or 1st namespace+localpart of the body.
I think a "Find" option might go a long way to solving this.

"Glen Daniels" <> on 11/02/2001 01:39:19 PM

Please respond to

To:   <>
Subject:  Re: tcpmon improvements

Would it be possible to make the HTTP/SOAP specific stuff optional?  Check
the appropriate boxes or specify command-line switches and you get the nice
extra features?


----- Original Message -----
From: "Doug Davis" <>
To: <>
Sent: Friday, November 02, 2001 10:00 AM
Subject: Re: tcpmon improvements

> I have some concerns about this...while tcpmon is written
> under Axis, my goal was to try to avoid making it too SOAP
> (and even HTTP) specific.  I've tried to make it just listen on
> sockets and that's about it.  Granted there are some cases
> where we do look at GET/POST and do something but
> if those aren't there we'll just keep going.  So a POST column
> might not be appropriate - but need to think about it.
> An OP column is truly too SOAP specific.  A Find pop-up could
> be really cool though!
> -Dug
> R J Scheuerle Jr/Austin/IBM@IBMUS on 11/02/2001 09:56:17 AM
> Please respond to
> To:
> cc:
> Subject:  tcpmon improvements
> Using tcpmon on the functional-tests can be cumbersome because of the
> number of messages.
> Here are some possible ideas for improvements to the port window:
>    Add a POST column which displays the value of the POST target.
>    Add a OP column which displays the name of the (SOAP) operation (if
>    present).
>    Add Find pop-up to search all messages for a given string.
> Volunteers?
> Rich Scheuerle
> ORB/IDLC Development
> 512-838-5115  (TL 678-5115)

View raw message