15.13.1 Trace collection points of CDI and the trace information that can be collected
This section describes the trace collection points of CDI and the trace information that can be collected. The following two cases will be described separately:
-
When a combination of JSF and CDI is used
-
When a combination of servlets and CDI is used
- Organization of this subsection
(1) Trace collection points and PRF trace collection levels
(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.
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 |
The following figure shows the trace collection points.
(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.
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 |
The following figure shows the trace collection points.
(2) Trace information that can be collected
(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.
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 |
(b) When servlets are invoked from CDI
The following table describes the 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:
|
2 |
0xb009 |
A |
CDIServiceImpl |
-- |
Entrance time |
Note that the trace information is collected when the servlet/filter/listener interfaces are generated.