Implementation note: rather than inject in its dependencies, we instead look up dependencies from the {@link IsisContext}. This is necessary, for the {@link PersistenceSession} at least, because class enhancers may hold areference to the factory as part of the generated bytecode. Since the {@link PersistenceSession} could change over the lifetime of the instance (egwhen using the {@link InMemoryObjectStore}), we must always look the {@link PersistenceSession} from the {@link IsisContext}. The same applies to the {@link ServicesInjectorSpi}.
Implementation note: rather than inject in its dependencies, we instead look up dependencies from the {@link IsisContext}. This is necessary, for the {@link PersistenceSession} at least, because class enhancers may hold areference to the factory as part of the generated bytecode. Since the {@link PersistenceSession} could change over the lifetime of the instance (egwhen using the {@link InMemoryObjectStore}), we must always look the {@link PersistenceSession} from the {@link IsisContext}. The same applies to the {@link ServicesInjector}.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|