-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
magnolia-personalization-pages
-
-
Empty show more show less
-
Yes
-
Nucleus 9
-
3
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
- is causing
-
PAGES-630 "Add component" before/after selected component is broken in 6.2.19
- Closed
- is cloned by
-
MGNLPN-632 Empty $type warning at startup
- Closed
1.
|
Provide a PR with a fix | Closed | Roman Kovařík | |||||||||
2.
|
Provide junit test | Closed | Roman Kovařík | |||||||||
3.
|
Provide docu PR | Completed | Roman Kovařík | |||||||||
4.
|
Code review | Completed | Sang Ngo Huu |
|
||||||||
5.
|
Docu review | Completed | Martin Drápela | |||||||||
6.
|
Port to cloud: PR review | Closed | Rabie Hayoun | |||||||||
7.
|
QA on master | Completed | Jaromir Sarf |