This week's book giveaway is in the Server-Side JavaScript and NodeJS forum.
We're giving away four copies of Modern JavaScript for the Impatient and have Cay Horstmann on-line!
See this thread for details.
Win a copy of Modern JavaScript for the Impatient this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

How to view the Soap Message

 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,
How do i view the actual SOAP Message which is being posted to MSSOAP WebServices?is there any API or do i have to see at the serverside?
Pls help me.
thanks,
Sachin
 
author and deputy
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is many tcp/ip sniffers available..

Like SOAP Monitor by Apache Axis.
TCP/IP monitor by http://www.pocketsoap.com/tcptrace/
and the best for your case is http://www.gotdotnet.com/team/tools/web_svc/default.aspx
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Sachin Dere:
Hi guys,
How do i view the actual SOAP Message which is being posted to MSSOAP WebServices?is there any API or do i have to see at the serverside?
Pls help me.
thanks,
Sachin



OK, I'm about a year behind the rest of ya'all, but I actually have the SOAP Monitor working!

Here's what I have learned ... (assumes Axis installed properly)

1) When compiling the SOAPMonitorApplet.java file, make certain that the resulting class files end up in the .../webapps/axis directory (I have a subdirectory called "monitors" where I do the build and deploy)
RESULT --> applet displays @ http://localhost:8080/axis/SOAPMonitor

2) Undeploy yourService - the one that you wish to monitor (assumes prior successful deployment)

3) Deploy SOAPMonitorService
RESULT --> SOAPMonitorService listed @ http://localhost:8080/axis/servlet/AxisServlet

4) Update WSDD for yourService to include the requestFlow/responseFlow handler tags (IN YOUR SERVICE), as per instruction #3 of "Enabling the SOAP Monitor" @ http://ws.apache.org/axis/java/install.html#AppendixEnablingTheSOAPMonitor

VERY IMPORTANT ... your service parameters go AFTER the requestFlow / responseFlow tags.

5) Redeploy yourService
RESULT --> YourService listed @ http://localhost:8080/axis/servlet/AxisServlet

Not sure if it matters, but I would suggest that the SOAPMonitorService always be deployed FIRST.

6) Undeploying the SOAPMonitorService. Not sure if this was my mistake, but
the undeploy-monitor.wsdd should specify
<service name="SOAPMonitorService"/>
NOT
<service name="urn:SOAPMonitorService"/>

This caused my server-config.wsdd to become corrupted. which leads me to item 7) Perform frequent backups of the .../webapps/axis/WEB-INF/server-config.wsdd file as you are learning and developing/updating services. This way, you can always recover to a working version (you will need to bounce your application server (Tomcat in my case)
before starting fresh.

Hope this helps whomever is behind me.

_DaX
 
    Bookmark Topic Watch Topic
  • New Topic