EclipseStoreContext - a better way to use ES?

[hrstoyanov]

I wanted to share EclipseStoreContext. The benefits it brings are:

• easy keeping track of objects to store (several add* methods), avoiding duplicates.
• bulk store.
• familiar commit/rollback api (commit, attemptCommit, rollBackOnly).
• [Optional] key generator and ES logging/versioning. These can be removed.

You pass around an EclipseStoreContext instance as method argument, or inject it in Spring/Microprofile (some supporting code is needed for that). But here I will show you how to use it with modern Java scoped values:

public class Products {
    public final static ScopedValue<EclipseStoreContext> ECLIPSE_STORE_CONTEXT = ScopedValue.newInstance();
    public static EclipseStoreContext getEclipseStoreContext() {
        return ECLIPSE_STORE_CONTEXT.get();
    }
}

...
 void filter (FilterChain chain, ServerRequest req, ServerResponse res) {

       var eclipseStoreContext = new EclipseStoreContext(embeddedStorageManager, maxPreserveVersion, tsidGenerator::generate);
       ScopedValue
                   // You can share context or use separate ones
                    .where(Users.ECLIPSE_STORE_CONTEXT, eclipseStoreContext)
                    .where(Products.ECLIPSE_STORE_CONTEXT, eclipseStoreContext)
                    .where(AuditEvents.ECLIPSE_STORE_CONTEXT, eclipseStoreContext)
                   //Other globals
                    .where(App.GLOBAl_APP_CONTEXT, this)
                    .where(HttpSession.Data.HTTP_SESSION_CONTEXT, httpSessionContext)
                   // Run the web stack chain
                    .run(chain::proceed);

       //Commit all accumulated changes
       eclipseStoreContext.commit();

}

void bizMethodDeepInTheCallChain(){
   var esc = Products.getEclipseStoreContext();
   ecs.addAllToPersist(o1);
   ...
   //Direct use of ES
   ecs.storeAll(o2);
   ...
   ecs.addAllToPersist(o3,o4,o5);
   ...
}

A few things I am too lazy/busy to do:

• remove string templates
• make the primary generator generic - use Supplier or whatever. Make this functionality optional (as well as versioning/logging).
• builder instead of constructor.

I believe the code is thread safe. NEVER PERSIT THE CONTEXT ITSELF!