Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-7634

Unresolved configured class names should be logged as error

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 6.1.2
    • node2bean
    • None

      When Map2BeanTransformer.readSimpleValue() line 197 encounters a class name that cannot be resolved, this problem is only logged as a "minor" and without details in DefinitionProviderProblemLogger line 89. 

      Not finding a class should be considered a major problem, as configuration and classpath don't match and this can lead to fatal problems. This should result in an ERROR being logged with details on configuration location and classname. Currently, this is logged as WARN instead, and without any details.

      More details currently are only logged if Magnolia is not in development mode, which doesn't make much sense anyway?

        Acceptance criteria

              Unassigned Unassigned
              jfrantzius Joerg von Frantzius
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: