uCosminexus Application Server, Maintenance and Migration Guide

[Contents][Glossary][Index][Back][Next]

8.25.2 Trace collection points in the processing between JSF and user applications

Organization of this subsection
(1) Trace collection points between a JSF application and a user application
(2) Trace collection points in resource handling

(1) Trace collection points between a JSF application and a user application

In a JSF application, the trace information is output when a user application is invoked.

(a) Trace collection points when a custom converter is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when a custom converter is invoked

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

Table 8-169 Details of the trace collection points when a custom converter is invoked

Event ID No. in the figure# Trace collection points Level
0xAF04 1 Immediately before a custom converter is invoked A
0xAF05 2 Immediately after the processing of the custom converter ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-108.

The following figure shows the trace collection points when a custom converter is invoked.

Figure 8-108 Trace collection points when a custom converter is invoked

[Figure]

Trace information that can be collected when a custom converter is invoked

The following table describes the trace information that can be collected when a custom converter is invoked.

Table 8-170 Trace information that can be collected when a custom converter is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF04 A #2 #3 --
2 0xAF05 A -- -- For an error, exception class name #4

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-108.

#2
The client ID of the component that invokes the user application is output.

#3
The class name and the method name of the custom converter are output.

#4
If ConverterException occurs because the user entered an incorrect value, the exception class name is output, but the processing terminates normally and the return code is 0.
Depending on when the custom converter is invoked from JSF, the exception processing terminates abnormally.
If you invoke the custom converter by specifying the <f:converter> tag of the UI component on the facelets page, only the component ID is displayed as the client ID.

(b) Trace collection points when a custom validator is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when a custom validator is invoked

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

Table 8-171 Details of the trace collection points when a custom validator is invoked

Event ID No. in the figure# Trace collection points Level
0xAF06 1 Immediately before a custom validator is invoked A
0xAF07 2 Immediately after the processing of the custom validator ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-109.

The following figure shows the trace collection points when a custom validator is invoked.

Figure 8-109 Trace collection points when a custom validator is invoked

[Figure]

Trace information that can be collected when a custom validator is invoked

The following table describes the trace information that can be collected when a custom validator is invoked.

Table 8-172 Trace information that can be collected when a custom validator is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF06 A #2 #3 --
2 0xAF07 A -- -- For an error, exception class name #4

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-109.

#2
The client ID of the component that invokes the user application is output.

#3
The class name of the custom validator is output. If you use MethodExpression to invoke the custom validator, MethodExpression is output.

#4
If ValidatorException occurs because the user entered an incorrect value, the exception class name is output, but the processing terminates normally and the return code is 0.

(c) Trace collection points when ValueChangeListener is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when ValueChangeListener is invoked

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

Table 8-173 Details of the trace collection points when ValueChangeListener is invoked

Event ID No. in the figure# Trace collection points Level
0xAF08 1 Immediately before ValueChangeListener is invoked A
0xAF09 2 Immediately after the processing of ValueChangeListener ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-110.

The following figure shows the trace collection points when ValueChangeListener is invoked.

Figure 8-110 Trace collection points when ValueChangeListener is invoked

[Figure]

Trace information that can be collected when ValueChangeListener is invoked

The following table describes the trace information that can be collected when ValueChangeListener is invoked.

Table 8-174 Trace information that can be collected when ValueChangeListener is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF08 A #2 #3 --
2 0xAF09 A #4 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-110.

#2
The client ID of the component that invokes the user application is output.

#3
The class name of ValueChangeListener is output. If you use MethodExpression to invoke ValueChangeListener, MethodExpression is output.

#4
When you invoke ValueChangeListener with MethodExpression and the processing terminates normally, one argument is output when a method with one argument is invoked and no argument is output when a method without arguments is invoked. A null character is output for an abnormal termination.

(d) Trace collection points when ActionListener is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when ActionListener is invoked

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

Table 8-175 Details of the trace collection points when ActionListener is invoked

Event ID No. in the figure# Trace collection points Level
0xAF0A 1 Immediately before ActionListener is invoked A
0xAF0B 2 Immediately after the processing of ActionListener ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-111.

The following figure shows the trace collection points when ActionListener is invoked.

Figure 8-111 Trace collection points when ActionListener is invoked

[Figure]

Trace information that can be collected when ActionListener is invoked

The following table describes the trace information that can be collected when ActionListener is invoked.

Table 8-176 Trace information that can be collected when ActionListener is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF0A A #2 #3 --
2 0xAF0B A #4 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-111.

#2
The client ID of the component that invokes the user application is output.

#3
The class name of ActionListener is output. If you use MethodExpression to invoke ActionListener, MethodExpression is output.

#4
When you invoke ActionListener with MethodExpression and the processing terminates normally, one argument is output when a method with one argument is invoked and no argument is output when a method without arguments is invoked. A null character is output for an abnormal termination.

(e) Trace collection points when AjaxBehaviorListener is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when AjaxBehaviorListener is invoked

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

Table 8-177 Details of the trace collection points when AjaxBehaviorListener is invoked

Event ID No. in the figure# Trace collection points Level
0xAF0C 1 Immediately before AjaxBehaviorListener is invoked A
0xAF0D 2 Immediately after the processing of AjaxBehaviorListener ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-112.

The following figure shows the trace collection points when AjaxBehaviorListener is invoked.

Figure 8-112 Trace collection points when AjaxBehaviorListener is invoked

[Figure]

Trace information that can be collected when AjaxBehaviorListener is invoked

The following table describes the trace information that can be collected when AjaxBehaviorListener is invoked.

Table 8-178 Trace information that can be collected when AjaxBehaviorListener is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF0C A #2 #3 --
2 0xAF0D A #4 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-112.

#2
The client ID of the component that invokes the user application is output.

#3
The class name of AjaxBehaviorListener is output. If you use MethodExpression to invoke AjaxBehaviorListener, MethodExpression is output.

#4
When the processing terminates normally, one argument is output when a method with one argument is invoked and no argument is output when a method without arguments is invoked. A null character is output for an abnormal termination.

(f) Trace collection points when Action Method is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when Action Method is invoked

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

Table 8-179 Details of the trace collection points when Action Method is invoked

Event ID No. in the figure# Trace collection points Level
0xAF0E 1 Immediately before Action Method is invoked A
0xAF0F 2 Immediately after the processing of Action Method ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-113.

The following figure shows the trace collection points when Action Method is invoked.

Figure 8-113 Trace collection points when Action Method is invoked

[Figure]

Trace information that can be collected when Action Method is invoked

The following table describes the trace information that can be collected when Action Method is invoked.

Table 8-180 Trace information that can be collected when Action Method is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF0E A #2 -- --
2 0xAF0F A -- -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-113.

#2
The client ID of the component that invokes the user application is output.

(g) Trace collection points when ComponentSystemEventListener is invoked and the trace information that can be collected
Trace collection points and PRF trace collection levels when ComponentSystemEventListener is invoked

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

Table 8-181 Details of the trace collection points when ComponentSystemEventListener is invoked

Event ID No. in the figure# Trace collection points Level
0xAF12 1 Immediately before ComponentSystemEventListener is invoked A
0xAF13 2 Immediately after the processing of ComponentSystemEventListener ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-114.

The following figure shows the trace collection points when ComponentSystemEventListener is invoked.

Figure 8-114 Trace collection points when ComponentSystemEventListener is invoked

[Figure]

Trace information that can be collected when ComponentSystemEventListener is invoked

The following table describes the trace information that can be collected when ComponentSystemEventListener is invoked.

Table 8-182 Trace information that can be collected when ComponentSystemEventListener is invoked

No. in the figure#1 Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF12 A #2 #3 --
2 0xAF13 A #4 -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#1
Corresponds to the numbers in Figure 8-114.

#2
The client ID of the component that invokes the user application is output.

#3
The class name of ComponentSystemEventListener is output. If you use MethodExpression to invoke ComponentSystemEventListener, MethodExpression is output.

#4
When you invoke ComponentSystemEventListener with MethodExpression and the processing terminates normally, one argument is output when a method with one argument is invoked and no argument is output when a method without arguments is invoked. A null character is output for an abnormal termination.

(2) Trace collection points in resource handling

A JSF application outputs the trace information when a requested resource is processed.

The trace can be collected in the following cases:

(a) Trace collection points and PRF trace collection levels

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

Table 8-183 Details of the trace collection points in resource handling

Event ID No. in the figure# Trace collection points Level
0xAF10 1 Immediately before the processing of the resource request starts A
0xAF11 2 Immediately after the processing of the resource request ends A

Legend:

A: Standard

#
Corresponds to the numbers in Figure 8-115.

The following figure shows the trace collection points in resource handling.

Figure 8-115 Trace collection points in resource handling

[Figure]

(b) Trace information that can be collected

The following table describes the trace information that can be collected in resource handling.

Table 8-184 Trace information that can be collected in resource handling

No. in the figure# Event ID Level Information that you can acquire
Interface name Operation name Optional
1 0xAF10 A -- -- --
2 0xAF11 A -- -- For an error, exception class name

Legend:
A: Standard
--: Not applicable

#
Corresponds to the numbers in Figure 8-115.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.