First ADR, inject repositories into Domain Object about crm-pilates

[bbougon]

Finally I mill reject my proposal.
Thanks to JB Dusseaut who gave me an excellent counsil, we don't need to create an event in order to create and persist all the sessions for a given class.
In fact, we know the pattern to create the session of a class, so as long as there is no domain event on a specific session, we don't need to persist it:

• it will ease the session management:
  • no need to update every persisted session in case of a class update
  • any action on the class or on the event has no need to deal with side effects on other sessions

knowing the pattern of the class, the domain can easily provide the informations of the upcoming events.
in case of an action on a session (e.g: checkin or cancel or whatever) we may apply it on the domain and then proceed to the persistence of the event.
All could be in memory at the domain level, we only need to load all the events at startup to retrieve the consistency