Hi Andrea,
yesterday, a colleague came across this same issue. The solution would indeed be to put a serialized event in the JobDataMap, instead of the plain message. Apparently, there is a setting to enable Java serialization (which was on by default in previous versions).
The QuartzScheduler allow you to customer the FireEventJob that is created, so you can extends both classes and change the behavior.
With my colleagues, we have already discussed a roadmap for Axon to migrate to using serialized Events instead, while maintaining compatibility with entries that still contain the serialized event. We didn't start yet, though.
Cheers,
Allard