Whenever automatic configuration or namespace whitelisting is used, class models generated through lazy-loading seem to fail silently (and returning null).

This makes it complex to identify the source of the actual error, if some POJOs are incorrectly defined, as the original model creation error is lost. A simple workaround is to explicitly add the class mentioned in the CodecConfigurationException, but that is painful, especially when multiple POJOs may actually be incorrect.

In such cases, we should log the error, to ease the debugging process.