Make critical errors occuring in DocumentModel EL resolver visible in logs an user interface

The custom DocumentModelResolver EL Resolver sometimes swallows critical errors, without logging them. The only errors that should be logged as warnings, and should not throw any error, are the ones about missing or non-existing properties (on set and get).
Other resolutions should be handled by existing EL resolvers (bean, map,...)