More error logging when Bean Validation throws an exception at startup
----------------------------------------------------------------------
Key: MYFACES-2932
URL: https://issues.apache.org/jira/browse/MYFACES-2932
Project: MyFaces Core
Issue Type: Improvement
Components: JSR-314
Affects Versions: 2.0.2
Environment: Any
Reporter: Jan-Kees van Andel
When the Bean Validation implementation fails to startup, for example because
it is misconfigured by the developer, or because of some dependency issue
(missing slf4j jar or something), the Bean Validator automatically turns itself
off.
The error is logged as "fine", because in many cases the developer doesn't care
about this behavior. For example, if bean validation api is provided, but impl
is not. In these cases, logging an error is not desirable.
But maybe this should be increased to "info", to ease debugging in the cases
where the developer is interested in why bean validation fails to startup.
I guess we change the logging to "info", especially because the block of code
is guarded by a Class.forName() check, which takes care of the obvious case
that Bean Validation is unavailable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
