Json Parser is too strict

The parser that handles the responses from the cloud foundry instance is very strict and aborts processing as soon as an unknown property is received or a type does not match. There is no easy way for applications using the cf-java-client to continue processing.
This becomes a problem if the versions of client and server do not match or if test coverage in the integration-tests does not point to the problem during development of a new version.

There should be some central switch to log and ignore problems during message parsing as far as possible. The switch would be helpfull during development, when client and server versions do not match.

There should be a configuration file to ignore only explicitly listed properties that are save to ignore, even in a productive environment.

No se nombran archivos, pruebas ni puntos de entrada. Empieza por localizar el analizador de mensajes de respuesta y su ruta de configuración existente; después, determina cómo se gestionan las propiedades desconocidas y las discrepancias de tipos. El trabajo terminado debe incluir una opción central para registrar e ignorar, así como una configuración para las propiedades ignoradas explícitamente, con cobertura para ambos comportamientos.