We are upgrading from 0.6 to 0.7 and noticed that the xml the
xmstreameventserializer creates is different than the one in 0.6. I
found the LegacyAxonEventUpcaster that makes sure the deserializing of
events keeps working. But it only works if I add this upcaster myself
to the xmstreameventserializer. Is this the idea? Or am I missing some
other configuration option?
Also it would be handy if a reference to the LegacyAxonEventUpcaster
was added to the migration notes in the release notes.
the fix was easy to spot. I decided to also include the fix in the 0.7 branch. Maven central will soon have a 0.7.1 version, that contains the fix. Meanwhile, you can download the 0.7.1 version from the downloads section on www.axonframework.org.
I thought it’s my mistake, as with many code / redeploy cycles I manage to bring system to the state where any event from repository would only have couple of fields from EventBase initialised, leaving all the rest as null. After that Java just crashed, and after restart everything worked well.
But if you say there was a bug, I’m glad I helped to spot it.