• Post Reply Bookmark Topic Watch Topic
  • New Topic

Axis webservice

 
rakesh verma
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Created webservice client using apache axis 1.1. Its working fine. But for debugging purposes, we need to look at request & response SOAP messages generated. So, is there anyway to do that.

Thanks in Advance.
 
Ulf Dittmer
Rancher
Posts: 42970
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Axis ships with the tcpmon tool, which can show you the SOAP request and response. It's documented here.
 
rakesh verma
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the response. But I can't run new applications in PROD and even by using this tool, it may slow down our processes.

Can't we do anything else just in the java code to log request/response messages.
 
Rahul Bhattacharjee
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by rakesh verma:
Thanks for the response. But I can't run new applications in PROD and even by using this tool, it may slow down our processes.

Can't we do anything else just in the java code to log request/response messages.


I have not yet started working with AXIS.But I think there should be a way to generate axis log.You have to go through the documentation as learn how you can enable logging in AXIS and how to specify the log file for that.
 
Ulf Dittmer
Rancher
Posts: 42970
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But I can't run new applications in PROD and even by using this tool, it may slow down our processes.


Performance should be a non-issue, since you said this is for debugging.

But if you're in fact talking about intercepting WS calls from some external client to a production server, then that's harder to do. The SOAPMonitor applet might help, but that, too, will have an impact on performance, as would any kind of logging.
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Apparently adding

inside the deployment element of your server-config.wsdd will log the requests and responses to "axis.log".

You may be able to use a different log file with:

though some people seem to have problems with this.

org.apache.axis.handlers.LogHandler
The file I/O will take its toll though. You could always write your own handler that logs to a faster resource.
[ May 25, 2007: Message edited by: Peer Reynders ]
 
rakesh verma
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Peer.

By using LogHandler, it creates logs in axis.log file in the path.

I extended LogHandler class with all the logging request/response needed and used that in the configuration file. Its working good.

Thank you guys
 
rakesh verma
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
One more question, I actually changed the descriptor file 'client-config.wsdd' in the jar file and repackaged it.
Is there any better way to do it. Like placing this file at some location and axis looks there (instead of repackaging jar everytime we have a change)
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!