axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walker, Jeff" <>
Subject RE: Axis and wss4j debugging
Date Fri, 03 Aug 2007 20:46:55 GMT
I don't know how to make Axis dump to stdout.

I had a similar issue a few weeks back. I was debugging Http headers on
the clientside.
I ended up subclassing HttpSender and making sure my new Sender class
got called by editing the client-config.wsdd file to pick up my class in
the transport tag. This allowed me to dump out all http headers in the
outgoing response. (You get access to the whole request as a string, if
I remember correctly). I had to add only a few lines here and there, but
it was a few hours determining the best places in my new subclass, then
it was 2 hours of painful debugging after that to determine how to make
Axis pick up my Sender instead of the expected HttpSender. But it did

I still think tcpmon or SoapMonitor are your best bet, on the
clientside. Especially, since all you want to do is look at the request
envelope going out and the response coming back.

-----Original Message-----
From: Hillel Seltzer [] 
Sent: Friday, August 03, 2007 4:19 PM
Subject: RE: Axis and wss4j debugging

Tried that, but nothing connected to tcpmon.

Is there anything that would force axis to dump to stdout
before attempting the remote connection?


On Fri, 3 Aug 2007 15:48:18 -0400, Walker, Jeff wrote
> If I remember correctly,
> edit the class that was generated for you.
> In it there is a hardcoded URL (created from the WSDL you supplied).
> Edit the port number in the class and make it like, 1234. Then put
> port number into tcpmon's "Listen Port #" field and copy the IP
> from the WSDL and put that into Target Host name, in tcpmon.
> I might have screwed up the steps slightly, but it's something like
> :)
> -jeff

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message