[MAGNOLIA-7634] Unresolved configured class names should be logged as error Created: 18/Sep/19 Updated: 23/Aug/21 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | node2bean |
| Affects Version/s: | 6.1.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Joerg von Frantzius | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Description |
|
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? |