Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2.0.15
-
None
-
magnolia-personalization-pages
-
-
Empty show more show less
-
Yes
-
AuthX 19
-
0.5
Description
Steps to reproduce
- Start Magnolia 6
- Check the startup-logs
- See the following warning:Â
WARN Â a.config.resolver.AnnotationProcessingTypeResolver: Encountered the '$type' property but failed to resolved the type from its value: [{}]. Available types: [jcrStatusColumn,variantAwareNameColumn,enumColumn,iconColumn,referredColumn,unhtmlColumn,columnComponent,jcrTypeColumn,iconAndValueColumn,koosCountColumn,jcrTitleColumn,jcrPathColumn,dateOnlyColumn,dateColumn]
Also check line 271 of info/magnolia/map2bean/Map2BeanTransformer.java and line 139 of info/magnolia/config/resolver/AnnotationProcessingTypeResolver.java
The reason why it fails, is that in info/magnolia/personalization/magnolia-personalization-pages/2.0.15/magnolia-personalization-pages-2.0.15.jar!/personalization-pages/decorations/pages-app/apps/pages-app.yaml we have the following piece of configuration:
(...) workbench: contentViews: tree: columns: jcrName: $type: !override class: info.magnolia.pages.app.browser.column.CachingVariantAwareTitleColumnDefinition (...)
Apparently, this is not the way to replace $type with another class; it reports an empty type.
Expected results
No warning should be logged on startup
Actual results
The logs are spammed with 50+ warnings
Workaround
-
Development notes
 the $type: !override can be safely removed and it worksÂ
Checklists
Acceptance criteria
Attachments
Issue Links
- clones
-
MAGNOLIA-8368 Class should take precedence over $type
-
- Closed
-
1.
|
QA |
|
Closed | Lam Nguyen Bao |
2.
|
Port to master |
|
Completed | Thuy To |