Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3260

ObjectTypeValidator should not reject unknown fields

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.0.0.Alpha1
    • None
    • Management
    • None

      As previously discussed on WFCORE-2249, ObjectTypeValidator is being more strict than our basic standard by rejecting unknown fields. When I did WFCORE-2249 I decided not to fix that. But now after working on some transformation stuff with complex attributes, I've changed my mind. If we don't relax this, transformers for complex attributes will have to remove even undefined fields from the attribute, which is fussy code.

      Transformers will have to do that anyway for hosts running versions prior to when this is fix is implemented but fixing this will help reduce how much that is required.

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: