Domain Events

[Amir2244]

Adding HasDomainEvent interface functionality, eg, registering, clearing for Aggregates, it's kinda like this :

public interface HasDomainEvents<T extends AggregateRoot<T,?>>
{
  void registerEvent(DomainEvent event);
  Collection<DomainEvent> DomainEvents();
  void ClearDomainEvents();
}

[Amir2244]

I'm working on a HasDomainEvents interface for aggregate event registration. I've identified a design tension: registerEvent must be public on the interface, which leaks encapsulation. Spring solves this with AbstractAggregateRoot (protected method). I see three paths:
(1) interface without registerEvent — SOLID-correct, registration left to the developer
(2) interface + abstract class companion
(3) accept the public leak with documentation.
Which direction fits best?