The feature-session-persistence, feature-state-management and feature-active-standby globalInit() functions initializes infrastructure such as the DroolsPdpIntegrityMonitor before the topic endpoints and controllers are up. This has the potential of causing issues in the future if a dependency ever exists on those infrastructure elements.  To avoid any issue, the initialization code should be moved to PolicyEngine.afterStart().

Then, you can remove the dependency on policy-core and remove the PolicySessionFeatureAPI implementation.

Care should be taken to assign sequence numbers so that the correct order of initialization is maintained between the feature-state-management and feature-active-standby-management.

Note that an instance of PolicyEngine is required on the call to afterStart().  In the JUnit implementation this can be accomplished by either creating a dummy PolicyEngine instance or passing PolicyEngine.manager to the method. See feature-eelf JUnits for example.