For debugging/logging purposes it would be useful to have a reasonable toString implementation for messages which is currently missing.
Looking at the source code org.axonframework.messaging.MessageDecorator could be a good start -
maybe the class of the message itself and the payload type should be included.
Are there further thoughts on the matter?
Just one thought: you鈥檙e right on this one. I would opt for more details in the toString, basically writing the message id, timestamp (for events), aggregate id and seq# (for domain event messages), meta data and payload.
I'll take care to create a PR for this.
Hi @pepperbob, hope you didn't get too far on the PR yet... I'm about ready to add my toString implementations.