MyFaces Core
  1. MyFaces Core
  2. MYFACES-2932

More error logging when Bean Validation throws an exception at startup

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.2
    • Fix Version/s: None
    • Component/s: JSR-314
    • Labels:
      None
    • Environment:
      Any

      Description

      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.

        Activity

        Jan-Kees van Andel created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Jan-Kees van Andel
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development