(a) When a combination of JSF and CDI is used

The following table describes the event IDs, trace collection points, and PRF trace collection levels.

Table 8-185 Details of the trace collection points when a combination of JSF and CDI is used

Event ID	No. in the figure#	Trace collection points	Level
0xb002	1	When the reading of the JSF settings required for using CDI starts	A
0xb003	2	When the reading of the JSF settings required for using CDI ends (normal termination)	A
0xb004	3	When the JSF preparations required for using CDI start	A
0xb005	4	When the JSF preparations required for using CDI end (normal termination)	A
0xb006	5	When the EL assessment starts	B
0xb007	6	When the EL assessment ends (normal termination)	B

Legend:

A: Standard

B: Advanced

#:

Corresponds to the numbers in Figure 8-116 and Figure 8-117.

The following figure shows the trace collection points.

Figure 8-116 Trace collection points when a combination of JSF and CDI is used (when the JSF settings are read and prepared)

Figure 8-117 Trace collection points when a combination of JSF and CDI is used (for EL evaluation)

(b) When a combination of servlets, filters, listeners, and CDI is used

The following table describes the event IDs, trace collection points, and PRF trace collection levels.

Table 8-186 Details of the trace collection points when a combination of servlets, filters, listeners, and CDI is used

Event ID	No. in the figure#	Trace collection points	Level
0xb008	1	When the generation of servlet/filter/listener instances starts	A
0xb009	2	When the generation of servlet/filter/listener instances ends (normal termination)	A

Legend:

A: Standard

#:

Corresponds to the numbers in Figure 8-118.

The following figure shows the trace collection points.

Figure 8-118 Trace collection points when a combination of servlets, filters, listeners, and CDI is used

(a) When a combination of JSF and CDI is used

The following table describes the trace information that can be collected when a combination of JSF and CDI is used.

Table 8-187 Trace information that can be collected when a combination of JSF and CDI is used

No. in the figure#1	Event ID	Level	Information that you can acquire
			Interface name	Operation name	Optional
1	0xb002#2	A	WeldFacesConfigProvider	--	Context information of the Web container
2	0xb003#2	A	WeldFacesConfigProvider	--	Entrance time
3	0xb004#2	A	WeldApplicationFactory	--	--
4	0xb005#2	A	WeldApplicationFactory	--	Entrance time
5	0xb006#3	B	WeldApplication	--	--
6	0xb007#3	B	WeldApplication	--	Entrance time

Legend:

A: Standard

B: Advanced

--: Not applicable

#1:

Corresponds to the numbers in Figure 8-116 and Figure 8-117.

#2:

The trace information for the reading of the JSF settings required for using CDI and for the JSF preparations required for using CDI is collected when the application starts.

#3:

The trace information for EL assessment is collected when FacesServlet is initialized and when Expression Language specified in JSF is evaluated.

(b) When servlets are invoked from CDI

The following table describes the trace information that can be collected when servlets are invoked from CDI.

Table 8-188 Trace information that can be collected when servlets are invoked from CDI

No. in the figure#	Event ID	Level	Information that you can acquire
			Interface name	Operation name	Optional
1	0xb008	A	CDIServiceImpl	--	The following information is output: Managed class Class name Context root
2	0xb009	A	CDIServiceImpl	--	Entrance time

Legend:

A: Standard

--: Not applicable

#:

Corresponds to the numbers in Figure 8-118.

Note that the trace information is collected when the servlet/filter/listener interfaces are generated.