Skip to main content

Message Logging in WSIT Updated

Posted by arungupta on December 4, 2006 at 6:51 PM PST

An update to original set of properties is now available.

THE FOLLOWING PROPERTIES ARE PROPRIETARY.  THEY CAN AND WILL CHANGE.

We are providing this information to help with development and debugging. 
These properties should not be used in deployments.

WSIT Pipeline
Assembler
exposes multiple system properties to enable SOAP message logging using
DumpPipe.
Each property, if it's value is set to true, injects a DumpPipe before or after
a WSIT component pipe in the pipeline. This allows the developer to monitor
message dumps at several points through out the pipeline, for example before and
after encryption. 

The legend that derives the property names is given below. A detailed list of
property names and their injection points are given in the table further below.
Example usages of these properties is given at the end. The table also shows a
convenience property, com.sun.xml.ws.assembler.XXX.action, that
displays only the wsa:To and wsa:Action header on XXX (client or server)
inbound and outbound messages.  

Legend:

  1. com.sun.xml.ws.assembler.client prefix indicates client-side
    properties
  2. com.sun.xml.ws.assembler.server prefix indicates server-side
    properties
  3. .after suffix indicates after (before) on client outbound
    (inbound) and server inbound (outbound).
  4. .before suffix indicates before (after) on client outbound
    (inbound) and server inbound (outbound). 

Table 1: List of property names and injection points

Property Name Location
Client-side Properties
com.sun.xml.ws.assembler.client Right before (after) the message is sent
(received) on client outbound
(inbound)
com.sun.xml.ws.assembler.client.action wsa:To and wsa:Action
header value on client outbound and inbound
com.sun.xml.ws.assembler.client.transport Right before (after) Transport pipe on client outbound
(inbound)
com.sun.xml.ws.assembler.client.wss.after Right after (before) SecurityPipe on client outbound
(inbound)
com.sun.xml.ws.assembler.client.wss.before Right before (after) SecurityPipe on client outbound
(inbound)
com.sun.xml.ws.assembler.client.wsrm.after Right after (before) RMPipe on client outbound (inbound)
com.sun.xml.ws.assembler.client.wsrm.before Right before (after) RMPipe on client outbound (inbound)
com.sun.xml.ws.assembler.client.wstx.after Right after (before) TxPipe on client outbound (inbound)
com.sun.xml.ws.assembler.client.wstx.before Right before (after) TxPipe on client outbound (inbound)
com.sun.xml.ws.assembler.client.wsa.after Right after (before) WsaPipe on client outbound (inbound)
com.sun.xml.ws.assembler.client.wsa.before Right before (after) WsaPipe on client outbound (inbound)
Server-side Properties
com.sun.xml.ws.assembler.server Right after (before) the message is received
(sent) on server inbound (outbound)
com.sun.xml.ws.assembler.server.action wsa:To and wsa:Action
header value on server inbound and outbound
com.sun.xml.ws.assembler.server.transport Right after (before) Transport pipe on server inbound
(outbound)
com.sun.xml.ws.assembler.server.wss.before Right before (after) SecurityPipe on server inbound
(outbound)
com.sun.xml.ws.assembler.server.wss.after Right after (before) SecurityPipe on server inbound
(outbound)
com.sun.xml.ws.assembler.server.wsa.before Right before (after) WsaPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wsa.after Right after (before) WsaPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wsmex.before Right before (after) MexPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wsmex.after Right after (before) MexPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wsrm.before Right before (after) RMPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wsrm.after Right after (before) RMPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wstx.before Right before (after) TxPipe on server inbound (outbound)
com.sun.xml.ws.assembler.server.wstx.after Right after (before) TxPipe on server inbound (outbound)

Example:

  1. If a message dump is required before and after the message is processed by
    WS-A pipe on the client outbound, then the following properties need to be
    set:



    -Dcom.sun.xml.ws.assembler.client.wsa.before=true and -Dcom.sun.xml.ws.assembler.client.wsa.after=true
  2. If a message dump is required before the message is sent and after it is
    received on the client, then the following property need to be set:



    -Dcom.sun.xml.ws.assembler.client=true 
  3. If all messages received by the RM pipe on server-side needs to be
    captured, then the following property need to be set:



    -Dcom.sun.xml.ws.assembler.server.wsrm.before=true

Notes:

  1. com.sun.xml.ws.assembler.client and com.sun.xml.ws.assembler.client.transport
    produce identical message dumps but allows an extensibility point if any
    other processing is required after the Transport pipe. This is also true for com.sun.xml.ws.assembler.server
    and com.sun.xml.ws.assembler.server.transport.

Technorati: WSIT SOAP
Web-services

Related Topics >>