Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Pulsar
-
Platform 222 - 14.0 Hangover, Platform 223 - 2019 Follow-up, Pulsar 234 - ContentSearch Fin
Description
Setting the parent bean of a Runtime Bean happens in 2 ways.
1) If the generated Runtime Bean has a supertype which is created in the same namespace, then this supertype is used as parent bean (if there are more than 1 supertypes which are created in the same namespace, than the first one is used).
2) If the generated RuntimeBean has no supertype which is created in the same namespace, then hippo:document, hippo:compound and hippogallery:imageset types are searched in the supertypes list. If any of them found, then it is used as supertype. If none of them is found, then an error is logged and the parent bean is set as null.
This logic should be improved to support other possible supertypes.
Attachments
Issue Links
- relates to
-
HSTTWO-4690 Dynamic beans support for content blocks doesn't generate method getContentBlocks for a contentblocks field added via essentials
- Closed
-
CMS-12869 Document how complex built-in types interact with the document type editor and the dynamic beans logic
- Closed
-
HSTTWO-4671 Improve runtime bean pojos to store more business logic
- Closed
-
HSTTWO-4696 Ensure dynamic beans generation works properly for content blocks fields when exposed via PageModel API
- Closed
-
CMS-12908 Dynamic beans: support cross namespace inheritance
- New