Interface CompositeSequenceReadService

All Known Implementing Classes:
CompositeSequenceReadServiceImpl

public interface CompositeSequenceReadService
Read-only retrieval service for CompositeSequence.

Phase 3 of the CompositeSequenceService decomposition (strangler fig). This service houses the pure DAO-delegate read cluster previously implemented directly on the CompositeSequenceServiceImpl facade: the findByBioSequence* / findByGene* / findByGenes* / findByName* lookups, findByNamesInArrayDesigns, the getGenes* variants, getGenesWithSpecificity, the getRawSummary variants, and thaw. All methods delegate to CompositeSequenceDao with no orchestration of other collaborator services.

Methods that compose multiple read collaborators (gene-mapping summaries, VO-enrichment with platform VOs) remain on the facade for now; they may be split into their own slice later.

Callers should generally keep using CompositeSequenceService as the facade — the facade delegates to this service. Direct injection is appropriate where a class would otherwise create a Spring construction cycle through the heavier facade.

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

See Also: