Interface ExperimentalFactorReadService
- All Known Implementing Classes:
ExperimentalFactorReadServiceImpl
ExperimentalFactor.
Phase 3 of the ExperimentalFactorService decomposition (strangler
fig). This service houses the single custom read method previously
implemented directly on the ExperimentalFactorServiceImpl facade:
thaw, which delegates to ExperimentalFactorDao.thaw(ExperimentalFactor).
Sibling read surfaces live in ExperimentalDesignReadService; the
read methods here operate on ExperimentalFactor directly and do not
overlap.
Write-side methods (the remove overrides plus the inherited
BaseService / AbstractVoEnabledService mutators) stay on the
ExperimentalFactorService facade.
Callers should generally keep using ExperimentalFactorService as the
facade -- the facade delegates to this service. Direct injection is
appropriate where a class is logically read-only.
ACL / @Secured annotations live on ExperimentalFactorService
(the caller-facing facade interface); enforcement happens at the facade
proxy boundary, not here. The new read impl is unsecured at the AOP boundary
on purpose -- intra-gemma-core callers that already hold an
authenticated session bypass duplicate ACL checks.
- See Also:
-
Method Summary
-
Method Details
-
thaw
-