10.3.10 Trace collection points of JAX-WS
The following describes the trace collection points of JAX-WS.
When collecting remote WSDL files
The following shows the trace collection points of JAX-WS when collecting remote WSDL files.
- Reference note
-
This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.
- #:
-
The part enclosed by the broken line is the same as the trace collection points of the web container when synchronous processing is used.
The following table lists event IDs, trace levels, trace collection points, and information that can be collected.
When collecting local WSDL files
The following shows the trace collection points of JAX-WS when collecting local WSDL files.
- Reference note
-
This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.
The event IDs, trace levels, trace collection points, and information that can be collected are the same as those of collecting remote WSDL files.
For a request-response operation (synchronous)
The following shows the trace collection points of JAX-WS for a request-response operation (synchronous).
- Reference note
-
This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.
- #1:
-
The part enclosed by the broken line is the same as the trace collection points of the web container when synchronous processing is used.
- #2:
-
The EJB container is called when EJB is implemented as the web service.
The collection points in the workflow after the EJB container is called are the same as those of local call of Session Bean and Entity Bean.
The following table lists event IDs, trace levels, trace collection points, and information that can be collected.
- #:
-
If the exception collected at a trace collection point is java.lang.reflect.InvocationTargetException, the name of the exception retained by java.lang.reflect.InvocationTargetException is output.
For a one-way operation
The following shows the trace collection points of JAX-WS for a one-way operation (synchronous).
- Reference note
-
This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.
- #1:
-
The part enclosed by the broken line is the same as the trace collection points of the web container when synchronous processing is used.
- #2:
-
The EJB container is called when EJB is implemented as the web service.
The collection points in the workflow after the EJB container is called are the same as those of local call of Session Bean and Entity Bean.
The event IDs, trace levels, trace collection points, and information that can be collected are the same as those in the details on the trace collection points of JAX-WS for a request-response operation (synchronous).
For a request-response operation (asynchronous)
The following shows the trace collection points of JAX-WS for a request-response operation (asynchronous).
- Reference note
-
This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.
- #1:
-
The part enclosed by the broken line is the same as the trace collection points of the web container when synchronous processing is used.
- #2:
-
The EJB container is called when EJB is implemented as the web service.
The collection points in the workflow after the EJB container is called are the same as those of local call of Session Bean and Entity Bean.
The event IDs, trace levels, trace collection points, and information that can be collected are the same as those in the details on the trace collection points of JAX-WS for a request-response operation (synchronous).