Why is DomainEvent not an interface?

I’m working on this monster task right now. It’s almost in a committable state, so just hang in there for just a while longer. I’m eager to find out what you all think of it.

Cheers,

Allard

Ladies and gentlemen: we’ve got him…

A few seconds ago, I committed this a monster-change (350 modified files) for this one. Since there was a nice and constructive discussion about this feature in this thread, I’d like to ask you to review the changes and tell me what you.

Cheers,

Allard

PS. One thing that I saw in the discussions that I haven’t done yet is remove Axon’s EventMessage (as it’s called now) from the public API interfaces. Therefore, (for example) EventBus still has a publish(EventMessage) method, instead of publish(Object).

Wow! It was indeed a heroic effort to implement the feature
in such a short time. Axon is getting better by the minute.

I built the framework and the address-book sample and ran the
sample with the web-ui interface on a Windows machine.
It compiled and passed the tests and ran flawlessly -- a rare
occurrence when a project is under development on a *nix
machine :slight_smile:

Congratulations and many thanks to the Axon team and
DutchWork for providing such a framework that is hands
down the best CQRS framework, in Java or otherwise.

Cheers,
Esfand

P.S. : I noticed a little issue with building the framework
       on a machine with an empty Maven repository, due to
       the dependency of third-party/disruptors's on the
       Axon framework and the dependency of the Axon framework
       on the disruptor module. The workaround was to comment-out
       the _parent_ element in the disruptor's pom.xml, build
       the framework, put the parent element back, and build
       the framework again to bootstrap the build. This has
       nothing to do with the new feature and showed-up when
       the disruptor module was added to the project.

My development is done on a Windows machine, but the Dutchworks build server runs on Ubuntu. So any OS-related glitches will quickly pop up.

Thanks for your positive words on Axon. However, it’s mostly the valuable feedback I get from the community that helped this framework foreward. So thanks to you!

Cheers,

Allard

PS. If you want to support Axon in another way: I’ve planned another workshop on January 27th. More information on http://www.dutchworks.nl/en/home/services/training.html

I totally agree with the congratulations made ​​by Esfand.
The work is really big and I have not yet had time to observe it completely, but I want to thank you all for giving the community a useful tool, and of such high quality.
I look forward to seeing the version 2 released, I guess for a revolutionary shift.

Cheers,
Domenico

Awesome! Unfortunately I'm rather slammed at the moment, I'll try to
look at it all by the weekend.

Chad