This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Considering you will be using JAX-RPC (or the new JAX-WS) or even Apache Axis, one way of logging your requests and responses is by implementing a Message Handler for that purpose. A Message Handler acts like a Servlet Filter, i.e., it intercepts your request before it reaches its destination (the endpoint) and intercepts the response before it is returned to the caller (the WS client). Both are very good times to log what is going back and forth.
You can write your Message Handler to use your favorite logging API, get the XML contents and post them to a log file.
I personally would recommend you to create a JAX-RPC (or JAX-WS) compliant Message Handler because that would make it reusable to any JAX-RPC compliant SOAP engine. And that means you could potentially use the same logging Message Handler on the client, on the server and on other applications. All you have to do is deploy it to the desired Web Service once it's complete.
Not in web.xml - it has nothing to do with servlet. You need to consult your Weblogic documentation about where handlers are declared. (For Axis, there is a deployment descriptor where this stuff goes, but Weblogic may work differently.)
Ping & DNS - updated with new look and Ping home screen widget
Joined: Jan 18, 2002
I'm not a Weblogic guy, but I was looking over the 8.1 docs and it seems it implements J2EE 1.3 and JAX-RPC 1.0. Being that the case, the method of deployment of Message Handlers is not mandated by the spec. See JAX-RPC 1.0 12.3.2. That changes for J2EE 1.4 when webservices.xml is used.