Oracle JHeadstart Developer's Guide - Downloads - Oracle

• which exceptions should be treated as expected exception, for which the stack
trace will never be written to the log.
• whether the error code (product code and error number) should be displayed.
Attention: To avoid losing your changes in the managed property values after
generating again, you should create a custom template based on the
JhsCommonBeans.vm template and make the changes in this custom template.
To use your custom template rather than the default template, select the
Service node in the Application Definition Editor, go to the Templates tab, and
set the value of template key JHS_COMMON_BEANS to the name of your
custom template. See chapter 4, section “Using Generator templates” for more
information on using custom templates.
Note that using the same technique of creating a custom template, you can use
your own subclass of ErrorReportingUtils when the exposed managed
properties are not sufficient to meet your specific needs.
Additional functionality implemented in this class relates to database errors. When the
underlying exception is a SQLException that indicates a database constraint violation, a
message with the constraint name as key will be added to the JSF Message stack, so you
can provide a user-friendly message to the user by adding this constraint name as key to
your message resource bundle. Note that the JHeadstart Application Generator already
generates such messages into your message resource bundle for all key constraints
defined in the XML file of your Entity Objects.
Reference: See the Javadoc or source of
ErrorReportingUtils.reportErrors
JHeadstart Developer’s Guide Internationalization 11- 13