Distinguish between Serializer for Events and general purpose serializer #270

Open
abuijze opened this Issue Feb 6, 2017 · 2 comments

Projects

None yet

2 participants

@abuijze
Member
abuijze commented Feb 6, 2017

While the XStreamSerializer is a sensible default, as it supports all object types, the JacksonSerializer is a better choice when it comes to storing Events.

The Configuration API should allow for this distinction, making it easier to serialize messages using the JacksonSerializer, while serializing aggregate snapshots and sagas using the XStreamSerializer by default.

In Spring, this distinction should somehow also be made.

@abuijze abuijze added the Enhancement label Feb 6, 2017
@abuijze abuijze added this to the Release 3.1 milestone Feb 6, 2017
@jorgheymans
Contributor

👍

just curious, why would the jacksonserializer be a better choice for events ?

@abuijze
Member
abuijze commented Feb 7, 2017

The generated json is not as tied to the classes as the json object is. Message payloads (and especially events) are generally inmutable objects with simple structure.

@abuijze abuijze self-assigned this Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment