10.3.10 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.

Figure 10‒23: 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.

Table 10‒25: Details on the trace collection points of JAX-WS (when collecting remote WSDL files)

Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
				Interface name	Operation name	Option
0xBA0A	1	Standard level	Before collecting WSDL files	Class name	Method name (number of parameters)	Endpoint URI
0xBA0B	2	Standard level	After collecting WSDL files	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name

When collecting local WSDL files

The following shows the trace collection points of JAX-WS when collecting local WSDL files.

Figure 10‒24: 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).

Figure 10‒25: 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.

Table 10‒26: Details on the trace collection points of JAX-WS for a request-response operation (synchronous)

Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
				Interface name	Operation name	Option
0xBA00	3	Standard level	The entry point of the service method of the stub-based SOAP client library	Class name	Method name (number of parameters)	-
0xBA01	8	Standard level	The exit point of the service method of the stub-based SOAP client library	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name
0xBA02	3	Standard level	The entry point of the service method of the dispatch-based SOAP client library	Class name	Method name (number of parameters)	-
0xBA03	8	Standard level	The exit point of the service method of the dispatch-based SOAP client library	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name
0xBA04	4	Standard level	Before sending the HTTP message of the SOAP client library	Class name	Method name (number of parameters)	Endpoint URI
0xBA05	7	Standard level	After receiving the HTTP message of the SOAP client library	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name
0xBA06	5	Standard level	Before calling the SOAP service (Web service implementation class)	Class name	Method name (number of parameters)	Service method name
0xBA07	6	Standard level	After calling the SOAP service (Web service implementation class)	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name#
0xBA08	5	Standard level	Before calling the SOAP service (Provider implementation class)	Class name	Method name (number of parameters)	-
0xBA09	6	Standard level	After calling the SOAP service (Provider implementation class)	Class name	Method name (number of parameters)	In a normal state - In an abnormal state Exception name#

#:

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).

Figure 10‒26: Trace collection points of JAX-WS (for a one-way operation)

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).

Figure 10‒27: 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).