-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Basel 46
-
3
As of MAGNOLIA-6451 we have introduced a utility which will read all the involved YAML files and combine their data into an aggregated map (=> Map2Bean etc).
It happens that if there's no data collected - a constant immutable empty map will be returned by map aggregating utility (Collections.emptyMap()). YamlDefinitionProvider however, could still attempt to push some metadata properties in that map, which causes exceptions with such a stacktrace: https://gist.github.com/p4elkin/1aac1845e017e2bb809547e5889f6a79
As of MAGNOLIA-6672 (and this commit) - a mutable map is returned and no such exception will occur any longer.
- caused by
-
MAGNOLIA-6451 YAML configuration: changes in included files don't trigger a reload of the registered item
- Closed
- is superseded by
-
MAGNOLIA-6672 Exceptions after YAML defined template is removed
- Closed
- relates to
-
MAGNOLIA-6662 Investigate JVM crash - and if faster DirectoryWatcher worsens it (Timebox)
- Closed