You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, when a GoogleGroupPartRepository is registered in a bounded context, the following exception is thrown:
java.lang.IllegalStateException: Aggregates of the repository io.spine.users.google.c.group.GoogleGroupPartRepository neither handle commands nor react on events.
The aggregate part only imports events. Probably, the design of the part should be changed.
The text was updated successfully, but these errors were encountered:
It's probably the bug in the repository registration code. If a repo only imports events, that's probably OK. It's not a usual case, but not necessarily a design flaw.
An aggregate, which only imports events looks like a projection. What's the reason to keep it as an aggregate instead of turning into a projection?
In this particular case, GoogleGroupPart applies external events related to a Google Group and mirrors the data about a Google Group in its state. Again, looks like it should be a projection.
Now, when a
GoogleGroupPartRepository
is registered in a bounded context, the following exception is thrown:java.lang.IllegalStateException: Aggregates of the repository io.spine.users.google.c.group.GoogleGroupPartRepository neither handle commands nor react on events.
The aggregate part only imports events. Probably, the design of the part should be changed.
The text was updated successfully, but these errors were encountered: