10.3.7 Trace collection points of JSF : Hitachi Application Server V10 User's Guide (For Windows Systems)

When a custom converter is called

The following shows the trace collection points of JSF when a custom converter is called.

Figure 10‒12: Trace collection points of JSF (when a custom converter is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒14: Details on the trace collection points of JSF (when a custom converter is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB700	1	Standard level	Immediately before a custom converter is called	Client ID	The class name and method name of the custom converter are collected.	-
0xB701	2	Standard level	Immediately after the processing of the custom converter ends	Client ID	The class name and method name of the custom converter are collected.	In a normal state - In an abnormal state Exception name

When a custom validator is called

The following shows the trace collection points of JSF when a custom validator is called.

Figure 10‒13: Trace collection points of JSF (when a custom validator is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒15: Details on the trace collection points of JSF (when a custom validator is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB702	3	Standard level	Immediately before a custom validator is called	Client ID	The class name of the custom validator is collected. If MethodExpression was used to call the custom validator, MethodExpression is collected.	-
0xB703	4	Standard level	Immediately after the processing of the custom validator ends	Client ID	The class name of the custom validator is collected. If MethodExpression was used to call the custom validator, MethodExpression is collected.	In a normal state - In an abnormal state Exception name

When ValueChangeListener is called

The following shows the trace collection points of JSF when ValueChangeListener is called.

Figure 10‒14: Trace collection points of JSF (when ValueChangeListener is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒16: Details on the trace collection points of JSF (when ValueChangeListener is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB704	5	Standard level	Immediately before ValueChangeListener is called	Client ID	The class name of ValueChangeListener is collected. If MethodExpression was used to call ValueChangeListener, MethodExpression is collected.	-
0xB705	6	Standard level	Immediately after the processing of ValueChangeListener ends	Client ID	In a normal state When ValueChangeListener is called by MethodExpression and ends normally, if a method with one parameter is called, `one argument` is output. If a method with no parameter is called, `no argument` is output. In an abnormal state -	In a normal state - In an abnormal state Exception name

When ActionListener is called

The following shows the trace collection points of JSF when ActionListener is called.

Figure 10‒15: Trace collection points of JSF (when ActionListener is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒17: Details on the trace collection points of JSF (when ActionListener is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB706	7	Standard level	Immediately before ActionListener is called	Client ID	The class name of ActionListener is collected. If MethodExpression was used to call ActionListener, MethodExpression is collected.	-
0xB707	8	Standard level	Immediately after the processing of ActionListener ends	Client ID	In a normal state When ActionListener is called by MethodExpression and ends normally, if a method with one parameter is called, `one argument` is output. If a method with no parameter is called, `no argument` is output. In an abnormal state -	In a normal state - In an abnormal state Exception name

When AjaxBehaviorListener is called

The following shows the trace collection points of JSF when AjaxBehaviorListener is called.

Figure 10‒16: Trace collection points of JSF (when AjaxBehaviorListener is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒18: Details on the trace collection points of JSF (when AjaxBehaviorListener is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB708	9	PRF trace collection level	Immediately before AjaxBehaviorListener is called	Client ID	The class name of AjaxBehaviorListener is collected. If MethodExpression was used to call AjaxBehaviorListener, MethodExpression is collected.	-
0xB709	10	Standard level	Immediately after the processing of AjaxBehaviorListener ends	Client ID	In a normal state When AjaxBehaviorListener is called by MethodExpression and ends normally, if a method with one parameter is called, `one argument` is output. If a method with no parameter is called, `no argument` is output. In an abnormal state -	In a normal state - In an abnormal state Exception name

When ActionMethod is called

The following shows the trace collection points of JSF when ActionMethod is called.

Figure 10‒17: Trace collection points of JSF (when ActionMethod is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

Table 10‒19: Details on the trace collection points of JSF (when ActionMethod is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB70A	11	Standard level	Immediately before ActionMethod is called	Client ID	-	-
0xB70B	12	Standard level	Immediately after the processing of ActionMethod ends	Client ID	-	In a normal state - In an abnormal state Exception name

When ComponentSystemEventListener is called

The following shows the trace collection points of JSF when ComponentSystemEventListener is called.

Figure 10‒18: Trace collection points of JSF (when ComponentSystemEventListener is called)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all of the triggers for collecting traces. Other triggers for collecting traces exist.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒20: Details on the trace collection points of JSF (when ComponentSystemEventListener is called)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB70C	13	Standard level	Immediately before ComponentSystemEventListener is called	Client ID	The class name of ComponentSystemEventListener is collected. If MethodExpression was used to call ComponentSystemEventListener, MethodExpression is collected.	-
0xB70D	14	Standard level	Immediately after the processing of ComponentSystemEventListener ends	Client ID	In a normal state When ComponentSystemEventListener is called by MethodExpression and ends normally, if a method with one parameter is called, `one argument` is output. If a method with no parameter is called, `no argument` is output. In an abnormal state -	In a normal state - In an abnormal state Exception name