guicedee/guicedee-client

GuicedEE Client

The client SPI library — defines the contracts that all GuicedEE modules program against without pulling in the full runtime.

Core Concept

This library provides the interfaces and annotations for the GuicedEE lifecycle. Application code and library modules depend on client to register hooks, access the injector, and define scoping — without coupling to the runtime engine in inject.

Required Flow

1. Add com.guicedee:client dependency.
2. Register your module for classpath scanning:

   IGuiceContext.registerModuleForScanning.add("my.app");
   IGuiceContext context = IGuiceContext.instance();
   Injector injector = context.inject();
   

3. Register hooks with JPMS provides:

   module my.app {
       requires com.guicedee.client;
       provides com.guicedee.client.services.lifecycle.IGuiceModule
           with my.app.AppModule;
   }
   

Lifecycle Hook Interfaces

All hooks extend IDefaultService<J> (CRTP) — override sortOrder() to control execution order and enabled() to conditionally skip.

| Interface | When | Purpose | |---|---|---| | IGuiceConfigurator<J> | First | Configure GuiceConfig before scanning | | IGuicePreStartup<J> | After scan, before injector | Pre-startup tasks, returns List<Future<Boolean>> | | IGuiceModule<J> | During injector creation | Standard Guice AbstractModule | | IGuicePostStartup<J> | After injector ready | Post-startup tasks, returns List<Uni<Boolean>> | | IGuicePreDestroy<J> | On shutdown | Cleanup resources |

Key Classes

| Class | Purpose | |---|---| | IGuiceContext | Singleton access to injector and context | | IDefaultService | Base for all SPI hooks (CRTP) with sortOrder() and enabled() | | CallScope / CallScopeProperties | Request-scoped injection context | | IJsonRepresentation | Jackson ObjectMapper configuration contract |

Non-Negotiable Constraints

• Module must requires com.guicedee.client;.
• All SPI implementations must be dual-registered (module-info.java + META-INF/services/).
• sortOrder() controls execution order — lower runs first.
• Lifecycle hooks are grouped by sortOrder() — all futures in a group must complete before the next group.