Yepp, I didn't remember if the JSON part of the work hierarchy was abstract or not.
But creating a new work class that inherits from AbstractJsonObjectWork that first checks if it is interesting and then if so pass it on to AbstractJsonObjectWork.

I'm just thinking around the changes you did before around rabbitmq where the event came in as json directly, and in that case this would be handy not having to parse it again.