Skip to content

Commit

Permalink
Update documentation to call out the dangers of calling Coherence ini…
Browse files Browse the repository at this point in the history
…tialization methods directly instead of solely relying on Injection.
  • Loading branch information
rlubke committed Sep 3, 2024
1 parent 323ed9f commit 6009789
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions src/main/docs/guide/bootstrap.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,5 +5,12 @@ By default, Coherence will start a single Session configured to use the default
This behaviour can easily be configured, either traditionally using Coherence system properties or using explicit Micronaut
configuration.

IMPORTANT: When using Micronaut, all Coherence resources used by application code should be injected.
Applications should avoid calling Coherence APIs that create or initialise Coherence resources directly,
especially static CacheFactory methods. If application code calls these Coherence APIs it may cause Coherence to
be initialised too early in the start-up process before the Micronaut framework has initialised the Coherence
extensions. A typical symptom of this would be that Coherence starts without picking up the correct configuration
from the Micronaut framework.



0 comments on commit 6009789

Please sign in to comment.