Question: shouldn't enrichMessageSchemaWithBase allow passing custom type field?

[Drodevbar]

This is a question rather than an issue. AbstractQueueService allows the custom messageTypeField property to be passed. On the other hand, enrichMessageSchemaWithBase always hardcodes message type as the type field, meaning that if a value other than type is configured on queue service, there will be a mismatch. I just want to make sure if that's expected behavior or whether it should be possible to pass a custom type field to enrichMessageSchemaWithBase as well.

EDIT: It's actually the same when it comes to id and timestamp

[kibertoad]

you are right! this makes sense to change