Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Turing Sprint 158, Turing Sprint 161 (7/18-8/1), Turing Sprint 162
Description
problem is that for example when I have a Spring addon module in the HST, for example
<module xmlns="http://www.onehippo.org/schema/hst/hst-addon-module_1_0.xsd">
<name>org.hippoecm.hst.pagecomposer</name>
<config-locations>
<config-location>classpath*:META-INF/hst-assembly/addon/org/hippoecm/hst/pagecomposer/*.xml</config-location>
<config-location>classpath*:META-INF/hst-assembly/overrides/addon/org/hippoecm/hst/pagecomposer/*.xml</config-location>
</config-locations>
</module>
it is now impossible to access the Spring beans of the page composer in downstream projects. This is because typically such a bean is not accessible during spring wiring. For example in a downstream project, I cannot use
<property name="pageComposerContextService" ref="pageComposerContextService"/>
even not when in the downstream project, I locate the addon below org.hippoecm.hst.pagecomposer, for example
org.hippoecm.hst.pagecomposer.otherproject
However, the HST spring component mngr should be able to support to access these beans. We want to support his by having the option to define a parent, for example
<module xmlns="http://www.onehippo.org/schema/hst/hst-addon-module_1_0.xsd">
<name>com.project.my.pagecomposer.extension</name>
<parent>org.hippoecm.hst.pagecomposer</parent>
Attachments
Issue Links
- clones
-
-
- Closed
-