FileBasedRouting shows a WARN when the message type can not be found

[HEskandari]

One of the usages of this package is to centralize the routing of messages. This means having one routing file, deployed to all endpoints and naturally, some message types might not be found at runtime.

Currently, the behavior is to log a WARN but that is undesired as it is an expected behavior.

Would be great to either remove it or have a way of controlling the behavior (opt in or out).

[timbussmann]

the problem is the fact that the endpoints need to read the whole file to see who could be interested in a published event. But this does't mean every reader need to load all types to make that verification. Some of those checks could probably be done via string comparison instead of loading types which makes the logic more resilient to "unknown" types.