-
Type:
New Feature
-
Status: Closed
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.0.0
-
Component/s: None
-
Labels:None
-
Similar issues:
-
Processed by team:Pulsar
-
Sprint:Platform sprint 131, Platform Sprint 132
If we allow annotations in HstComponent classes like Spring Framework's @Component, then we can probably allow any Spring AOP techniques without having to provide new interfaces like DoBeforeRenderExtension of Essentials.
As a briefing:
- Developers annotate HstComponent classes with an annotation (e.g, @Component).
- Spring Framework application context loads @Component beans as 'prototype' beans since we need a separate HstComponent instance per HST component configuration even if the hst component classname is the same.
- Then HST Component Factory always get a reference of the HstComponent bean managed by Spring Framework ApplicationContexts (of HST ComponentManager).
HST Component Factory can be backward-compatible for non-annotated component classes in this approach. It can load it from the HST Component Manager first, for instance. - developers can use Spring AOP techniques.
One advantage here is developers can control in any granularity with the point cut configuration.