-
1. Re: axis tcpmon
thomas.diesler Apr 22, 2005 4:38 AM (in response to golubec)How is this related to JBoss? The exception seems to indicate that commons-logging.jar is missing from your classpath.
-
2. Re: axis tcpmon
golubec Apr 22, 2005 9:23 AM (in response to golubec)web services in JBOSS documentation are examined by this way : through tcpmon. So i've thought that at JBOSSWS i can find the people experienced with this utility. I need to analyze SOAP traffic and look for appropriate toolkit. As i see some use Ethereal but unfortunely it doesnt' provide traffic information for localhost.
-
3. Re: axis tcpmon
thomas.diesler Apr 22, 2005 10:02 AM (in response to golubec)tcpmon is feed by a propriatory Axis handler, which cannot be used in WS4EE. JBossWS exposes the SOAP messages through standard logging.
-
4. Re: axis tcpmon
golubec Apr 22, 2005 11:27 AM (in response to golubec)i'm not so strong in JBOSS details and i want to use tcpmon just like external SOAP sniffer - that's all. But i little confused with you post 'cos it's claimed at jbossws-wiki jbossws is based at apache-axis.
-
5. Re: axis tcpmon
thomas.diesler Apr 22, 2005 3:20 PM (in response to golubec)True, WS4EE is currently based on a modified version of axis-1.1. This is an implementation detail that will be removed with the JBossWS rewrite.
Nevertheless, with WS4EE you *cannot* use an axis handler that feeds tcpmon.
You are of course free to use any WS client you like (e.g. standalone axis with tcpmon), but then its not an jboss issue