Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce DomainEventHydratorManager #5

Closed
codeliner opened this issue May 23, 2014 · 1 comment
Closed

Introduce DomainEventHydratorManager #5

codeliner opened this issue May 23, 2014 · 1 comment
Labels
enhancement

Comments

@codeliner
Copy link
Member

It is not enough to only use the FQCN of an Event as identifier to reconstruct the event from a stream. A DomainEventHydratorManager could provide more strategies to reconstruct events.

Posibilities could be:

  • different Versions of same event
  • Shared Events
  • ...

FQCN should be translated to dot notation or events implement EventNameProviderInterface
@codeliner
Copy link
Member Author

Move functionality out of the adapter. The adapters should only work with the extracted event data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@codeliner