Hi, When using Axis2 as a client, the logging of the HTTP requests and responses messages can be activated by using the "httpclient" package in the log4j configuration. When calling a webservice, the Axis2 client uses an HTTP connection for the communication with the server. Activating the logging allows us to see the "raw" SOAP message and some additional information (>> "POST /fourthway/1.0/NoticeRequesterInterface HTTP/1.0[\r][\n]", >> "SOAPAction: "http://..."[\r][\n]";, ...). Once the webservice has been called, a synchronous HTTP response is received that contains for instance: "HTTP/1.1 200 OK".
I have tried to achieve the same logging information when using Axis2 as a server, but without success :-(. What I would like to achieve, is the following: log every HTTP request to my Axis2 server on the HTTP level, i.e. the "raw" SOAP message that traverses the wire and log every HTTP response that my Axis2 server sends to the client. I suppose that - similar as in the client scenario - when a client calls my Axis2 server, an HTTP connection is established that allows the transport of the SOAP message. Activating the "httpclient" package in the log4j configuration of my Axis2 server, is not sufficient to log this kind of information. I've seen some posts and the explanation on how to add LoggingHandlers in the Axis2 process flow, but I think that this kind of logging does not log on the HTTP request/response level. What's the best way to log HTTP requests and responses when using Axis2 as a server ? Regards, Stefan Lecho. -- View this message in context: http://www.nabble.com/Log-of-request-response-on-transport-level-tp15268442p15268442.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
