Details
-
New Feature
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Turing Sprint 164, Turing Sprint 165, Turing Sprint 166, Turing Sprint 167, Turing Sprint 168
Description
HST Spring Bean Bridge [1] component allows to manage hst component beans in spring framework dependency injection. It's good for some use cases.
One tedious situation is it cannot change ParametersInfo annotation easily for each component configuration to use in channel manager unless you extend the bridge class every time only for this annotation change.
So, I think it would be better if we support an optional hst component configuration parameter like hst:parametersinfoclassname in a component configuration.
If the property is set to a FQCN, HST container should use it to load parameters info class instead of annotation scanning.
Ard:
The property should take a precedence over the annotation. This way we also gain the possibility to have one and the same component class popup with different component window properties (because not compile time hard coded but overridable.
This way, we can make it easy to use that kind of component bridges.
[1] http://www.onehippo.org/library/concepts/web-application/spring-bridge.html
Attachments
Issue Links
- is duplicated by
-
CHANNELMGR-280 hst:parametersinfoclassname optional property for easy use of HST Spring Bean Bridge component
- Closed
- relates to
-
HSTTWO-3405 ParametersInfo annotation present on HstComponent superclass does not work
- Closed