-
Improvement
-
Resolution: Obsolete
-
Neutral
-
None
-
5.5.2
-
None
-
None
With introduction of MAGNOLIA-6901, we gave users possibility to implement custom resolvers. Our error/warning handling mechanism is only taking default resolver with 'class' property into account and should be replaced by a more generic solution which handles custom ones as well.
Acceptance criteria
- caused by
-
MAGNOLIA-6901 Generalise bean type resolution strategy in to-bean transformers
- Closed
- duplicates
-
MAGNOLIA-6928 TypeResolvers do not report any problems making it hard to identify issues with definitions
- Accepted