HST Core Spring Extension Points
The HST core exposes a number of Spring-managed bean IDs which a Bloomreach Experience Manager project can use or override.
When a project is entitled to use a Spring bean managed by the HST core (retrieving it through HST's ComponentManager or injecting it into a project-specific Spring bean through configuration, such as a constructor argument or by calling a setter on the bean), we declare that bean as API.
When a project is entitled to override a Spring bean managed by the HST core (by defining a project-specific Spring bean with the same ID), we declare that bean as SPI (service provider interface).
Here is a list of Spring beans managed by the HST code and intended for API or SPI usage by projects.
Spring Bean ID | Usage |
---|---|
org.hippoecm.hst.platform.HstModelProvider | API |
customChannelFilters | SPI |
customChannelManagerEventListeners | SPI |
hstJmvEnabledUsers (lab) | API |
javax.jcr.Credentials.default | API |
javax.jcr.Credentials.default.delegating | API |
javax.jcr.Credentials.preview | API |
javax.jcr.Credentials.preview.delegating | API |
javax.jcr.Credentials.writable | API |
javax.jcr.Credentials.hstconfigreader | API |
javax.jcr.Credentials.hstconfigreader.delegating | API |
javax.jcr.Credentials.binaries | API |
javax.jcr.Repository | API |
javax.jcr.Repository.delegating | API |
javax.jcr.Repository.subjectBased | API |
org.hippoecm.hst.core.request.ContextCredentialsProvider (lab) | SPI |
org.hippoecm.hst.security.AuthenticationProvider | SPI |
org.hippoecm.hst.core.linking.HstLinkProcessor | SPI |
org.hippoecm.hst.core.linking.HstLinkCreator.binaryLocations | SPI |
org.hippoecm.hst.core.linking.RewriteContextResolver | SPI |
customResourceResolvers | SPI |
customResourceContainers | SPI |
customJcrObservationEventListenerItems | SPI |
org.hippoecm.hst.core.container.PageErrorHandler | SPI |
Usage of other HST core Spring beans is not guaranteed to be stable across releases, and therefore strongly discouraged.