With application development using the CDI, you can use the check development log as the debug log.
If there are errors or defects in the CDI application being developed, you can use the check development log to check the cause and to understand the detailed operations of the target functionality.
With the applications that use the CDI, the development-related messages are output to the check development log. The messages that require confirmation with the applications that use the CDI can be identified from the class name output to the message. The following table describes the components that output the messages and the class name that is output.
Table 9-5 Class names output to the check development log for the applications that use the CDI
Component name | Output class name | Output contents |
---|---|---|
CDI | com.hitachi.software.cdi.weld.- com.cosminexus.cc.lib.jboss_interceptor.v2_0_0_CR1.- |
|
Note that the check development log is not output by default. Change the settings as and when required.
For details on the settings to output the check development log, and the output destination, output format, and log levels of the check development log, see 24.4 Messages output for the check development log in the manual uCosminexus Application Server Messages.
Also, for details on the check development log for Bean Validation used with the CDI applications, see 10.6 Using the debug log (check development log).