AxonFramework/AxonFramework — Issue #18: Improve Event API by extracting application-specific payload
Author: abuijze
Created: 2011-12-03 14:50:20+00:00
State: open
Labels: Awaits Documentation

**What are the limitations you encounter in the current version? Please provide a simple use-case.**
The current Event implementation structure requires applications to create Events that extends one of the Axon provied implementations, e.g. DomainEvent.
Axon will add some extra information in these events, needed to identify the aggregate it belongs to and the order in which events should be read back in.

**Please describe the enhancement you would like to have.**
In the discussion group (http://groups.google.com/group/axonframework/browse_thread/thread/9e88daef9ff5e61f), Esfand suggested to introduce an explicit "payload". This payload is an application-provided POJO, untouched by Axon. Axon will keep its meta-data separate from that payload.

**Do you have any ideas on how to implement the enhancement? If so, any suggestions are welcome.**
See http://groups.google.com/group/axonframework/browse_thread/thread/9e88daef9ff5e61f.