FAQ

How do I override the CRISP API module version in my project?

The parent release POM (hippo-cms7-release or hippo-cms7-enterprise-release) defines a default version of the CRISP API. If a newer maintenance release is available and you want to use it, override the hippo.addon-crisp.version property in your project's root POM. For example:

  <properties>
    <!--***START temporary override of versions*** -->
    <!-- SNIP -->
    <hippo.addon-crisp.version>13.0.0</hippo.addon-crisp.version>
    <!-- ***END temporary override of versions*** -->
    <!-- SNIP -->
  </properties>
copy

This configuration sets the hippo.addon-crisp.version property to the specified version, replacing the default version provided by the parent POM.

Can I map Resource objects to domain-specific POJOs?

Yes. POJO mapping is supported starting from version 2.1.1. For implementation details, see the POJO Mapping Support documentation.

How do I override internal CRISP beans?

Internal CRISP beans are defined in the hippo-addon-crisp-core-x.x.x.jar!META-INF/spring-assembly/addon/crisp/crisp*.xml resources. To override a bean, redefine it in a file located at site/components/src/resources/META-INF/hst-assembly/addon/crisp/overrides/*.xml. For example, you can override the org.springframework.http.client.ClientHttpRequestFactory bean to customize HTTP client connection handling.

Can I use CRISP in non-CMS delivery or authoring tier applications?

Yes. The CRISP API and core modules do not depend on CMS-specific APIs. You can use CRISP in both delivery-tier and authoring-tier applications.

Can I use the Circuit Breaker Framework with the CRISP API?

Yes. For implementation guidance, see Circuit Breaker Pattern with CRISP API.

Which is more crisp: Granny Smith apples or CRISP?

If your focus is on baking or cooking, Granny Smith apples may seem crisper. If you are working on backend integrations in content delivery or authoring tiers, you will likely prefer CRISP.