+1!!! Are you planning to make more tests demonstrating how you manage replay of events and the like? That would be really helpful to learn from, although I'm now trying to see how you have done in Streamflow.
I'm thinking of doing: 1) receive HandlingEventRegistrationAttempt via some web interface 2) call @DomainEvent createdHandlingEvent( HandlingEventRegistrationAttempt ) 3) have a listener to (asynchronously) inspect the Cargo upon a HandlingEvent creation event. Does this sound reasonable as a better alternative than using JMS messaging? (Or is it two different things? I'm new to both...) Is it correct that - from this approach - you would get the benefit of creating the handling event independently of inspecting (and updating the Delivery History) of the Cargo? In the DDDsample they don't want to involve the bigger cargo aggregate everytime series of Handling Events are registered. Maybe it's not even a problem in the way Qi4j stores data? (now I'm on deep water). Great work!! It's hard to keep up :) Cheers, Marc On 19/01/2011, at 09.58, Rickard Öberg wrote: > I have now made an initial commit of an EventSourcing library in > qi4j-libraries. _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
