Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-6531

Do not always throw exceptions to propagate information about failed validations

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Models Validation Impl 1.0.0
    • Models Validation Impl 1.0.0
    • Extensions
    • None

    Description

      Right now the o.a.s.models.validation.impl.ModelValidationImpl will always throw an InvalidResourceException in case the underlying resource is not valid (according to Sling Validation). With the advent of different severities per issue (SLING-5373) this seems a bit too strict because some validators could be used just for informational purposes. Those validations should not prevent the Sling Model from being instantiated.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SLING-6534 Optionally cache results of ValidationService.validate(Resource, ValidationModel) and expose the cached result via an AdapterFactory

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SLING-5373 Allow different severities per validator

          • Major - Major loss of function.
          • Closed

          Activity

            People

              kwin Konrad Windszus
              kwin Konrad Windszus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: