Sometimes, there could be newer versions (as results of mainteance releases) than the default version of CRISP API pulled in by the parent release pom (hippo-cms7-release or hippo-cms7-enterprise-release) dependency of your project.
If you want to use a newer maintenance release version in your project, you can override hippo.addon-crisp.version property in the root pom like the following example:
<properties> <!--***START temporary override of versions*** --> <!-- SNIP --> <hippo.addon-crisp.version>2.0.5</hippo.addon-crisp.version> <!-- ***END temporary override of versions*** --> <!-- SNIP --> </properties>
So, in the example shown above, it is overriding the default hippo.addon-crisp.version property to use the specified version instead of the default version pulled in transitively by the parent release pom dependency.
Yes, POJO mapping has been supported since v2.1.1. See POJO Mapping Support page for details.
All the internal CRISP beans are defined in hippo-addon-crisp-core-x.x.x.jar!META-INF/spring-assembly/addon/crisp/crisp*.xml resources. If you want to override any bean, you can redefine a bean in site/src/resources/META-INF/hst-assembly/addon/crisp/overrides/*.xml file. For example, you can override org.springframework.http.client.ClientHttpRequestFactory bean for more advanced HTTP Client Connection handlings.
Yes, CRISP API and CORE is basically independent from CMS specific APIs. However, you will need to include all the provided dependencies referred by CRISP API and CRISP Core by yourself in your application.
Yes. Please see Circuit Breaker Pattern with CRISP API page for detail.
Depends. If you're more interested in baking or cooking than programming, perhaps Granny Smith apples look more crispy, but if you have struggled with implementing backend integrations in content delivery or authoring tier on and on, probably you will pick CRISP.