Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Flagged
-
Platform 220 - Hardening, Platform 221 - 14.0 CodeFreeze, Platform 222 - 14.0 Hangover, Platform 223 - 2019 Follow-up, Platform 227 - Taxonomy 2
Description
This relates to Spring wired Components, also see [1]
We need to take into account spring wired components. If we do that correctly, we can also drop the requirement in [1] wrt "You should set @hst:parametersinfoclassname property (since v12.1) to specify the FQCN of the component parameters info interface (which is equivalent to the type attribute of org.hippoecm.hst.core.parameters.ParametersInfo annotation in the component class. So, the component parameters info can be scanned by the new @hst:parametersinfoclassname property value if needed (while using Channel Manager for instance)." since we can just fetch the HstComponent. However, we need to fetch the HstComponent from the correct HST ComponentManager, this involves a set of changes and making sure that via a classloader we can retrieve the correct ComponentManager
Attachments
Issue Links
- causes
-
HSTTWO-4380 ParametersInfoAnnotationUtils: Don't log warning in case where spring component id is used instead of component classname
- Closed
- is awaited by
-
HSTTWO-4620 Loading of ParametersInfo class fails within channel manager
- Closed
- relates to
-
CMS-12849 Redesign how PageComposer loads ParametersInfo objects from site
- Open
- waits for
-
HSTTWO-4564 Support getting hold HST Website Spring Component Manager by Classloader
- Closed