Skip to content

Extensible registrar mechanism for JS-declared server extension points #691

Description

@romain-pm

Part of EPIC #554. Implemented — under review in #687.

Shared AbstractServiceRegistrar<S> base: per-bundle registry discovery, bridge creation, OSGi service publication (whiteboard-tracked by core), tracked unregistration with per-entry error isolation. One registrar component per extension type; a future extension point is one subclass + one typed library wrapper. The legacy render-filter bridging was migrated onto the mechanism (its declared priority is now honored — changelog-noted behavior change) and got a typed registerRenderFilter() API, with async callbacks supported (#688).

Decisions: ADR-0001 (mechanism, whiteboard alignment), ADR-0002 (first-class registry types), ADR-0003 (typed TS wrappers + java escape hatch).
Tests: AbstractServiceRegistrar unit tests; existing render-filter e2e stays green.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions