Interface BioAssayReadService

All Known Implementing Classes:
BioAssayReadServiceImpl

public interface BioAssayReadService
Read-only retrieval service for BioAssay.

Phase 3 of the BioAssayService decomposition (strangler fig). This service houses the DAO-bound read cluster previously implemented directly on the BioAssayServiceImpl facade: findBioAssayDimensions, findByShortName, findByAccession, findSubBioAssays, findSiblings, getBioAssaySets, thaw (x2), loadValueObjects, loadValueObjectsByCursorForExpressionExperiment, and loadValueObjectsByCursorForSubSet. All methods delegate to BioAssayDao (and read-side collaborators) and orchestrate no writes.

Write-side methods (addBioMaterialAssociation, removeBioMaterialAssociation, plus the inherited BaseService mutators) stay on the BioAssayService facade.

Callers should generally keep using BioAssayService as the facade -- the facade delegates to this service. Direct injection is appropriate where a class is logically read-only (REST endpoints, CLIs, browser controllers, intra-core readers).

ACL / @Secured annotations live on BioAssayService (the caller-facing facade interface); enforcement happens at the facade proxy boundary, so this interface is intentionally unsecured.

See Also: