uCosminexus Application Server, Web Container Functionality Guide

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

3.7 Using log (development investigation log) for debugging

You can use the development investigation log for debugging during the JSP application development.

You can use the development investigation log to investigate the cause or to understand more details on the behavior of the concerned functionality if an error occurs or a bug is detected during the development of a JSF application.

The JSF application outputs the development related messages to the development investigation log. While debugging the JSF application, you can identify the messages to be noted, with the respective class names that are output in messages. The following table describes the components that output the messages and the respective class names that are output.

Table 3-14 Class names output in the development investigation log of the JSF application and the Bean Validation

Component name Class name output Output content
JSF javax.faces.~
com.sun.faces.~

  • Error messages
  • Messages reporting incorrect settings
  • Exception stack trace
  • Messages about the execution status of functionalities
  • Messages about the internal status

Note that the development investigation log is not output if the default settings are used. You need to change the settings as and when required.

For details such as the settings required to output the development investigation log, the output destination of log, the output format, and the log level, see 24.4 Messages output in the development check log in the uCosminexus Application Server Messages.

Also, for details on the development investigation log of Bean Validation used in the JSF application, see 10.6 Using log (development investigation log) for debugging in the uCosminexus Application Server Common Container Functionality Guide.