SOAP Message handler

[Dominik Świątek]

I have generated WebService client using wsdl2java (axis2-1.5). Client 
is working fine, i can call methods and receive correct results. Now I 
would like to intercept incoming and ougoing SOAP Messages to save them 
to file for reference. Question: how i do this? Right now i'm 
hand-editing generated ServicesStub but this is both ugly and 
inconvinient. Is there something simmilar to JAX-WS SOAPHandlers in Axis?

Re: SOAP Message handler

[Deepal Jayasinghe]

You need to write a module with two handlers [1], and then just engage
the module to the service client.

[1] : http://blogs.deepal.org/2009/02/writing-axis2-module.html

Thanks,
Deepal

Dominik Świątek wrote:
 I have generated WebService client using wsdl2java (axis2-1.5). Client
 is working fine, i can call methods and receive correct results. Now I
 would like to intercept incoming and ougoing SOAP Messages to save
 them to file for reference. Question: how i do this? Right now i'm
 hand-editing generated ServicesStub but this is both ugly and
 inconvinient. Is there something simmilar to JAX-WS SOAPHandlers in Axis?


-- 
Thank you!


http://blogs.deepal.org
http://deepal.org

Message Handler

[Anne Vetter]

I'm trying to implement a handler to process SOAP headers.Now, I've got one major problem.Do I have to deploy that handler separately? My WS works without handlers ... but as soon as I implement my handler in the 
deploy.wsdd file it just won't work any more. If I deploy the handler first and then try to deploy the WS, Axis tells me:Exception - org.apache.axis.ConfigurationException: Can't find handler name:'null' type:'AuthenticationHandler' in the registry
org.apache.axis.ConfigurationException: Can't find handler name:'null' type:'AuthenticationHandler' in the registry	at org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:129)	at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance
(WSDDDeployableItem.java:274)	at org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)	at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:430)
	at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:503)	at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:296)	at org.apache.axis.transport.http.AxisServlet.reportAvailableServices
(AxisServlet.java:482)	at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:260)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)	at org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:327)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)	at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173)	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)	at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)	at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:107)	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
(Http11BaseProtocol.java:664)	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)	at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)	at java.lang.Thread.run(Unknown Source)I just seem not to be able to solve that myself. I've tried to look for detailed information online, and I've found plenty of stuff about handlers themselves, but not really much about their deployment.