- v1.0.0-latest-prod
This document covers the miscellaneous configuration properties used by the Content Services.
All content cache properties are related to the time-to-live for each cache. The defaults are 5 minutes. These are all also to facilitate caching when resolving Content Items in the various possible ways.
broadleaf.content.cache.by-model-name: Caches results when looking up a Content Model by name.
broadleaf.content.cache.by-model-uri: Caches results when looking up a Content Model by uri.
broadleaf.content.cache.by-item-name: Caches results when looking up a Content Item by name.
broadleaf.content.cache.by-item-id-in: Caches results when looking up Content Items by multiple context Ids.
broadleaf.content.cache.by-item-name-in: Caches results when looking up Content Items by multiple names.
broadleaf.content.cache.by-item-uri-and-model-id: Caches results when looking up a Content Item by URI and a Model Id.
broadleaf.content.cache.page-by-item-name-in: Caches results when looking up a page of Content Items by multiple names.
broadleaf.content.cache.page-by-item-id-in: Caches results when looking up a page of Content Items by multiple context Ids.
broadleaf.content.cache.page-by-item-model-id: Caches results when looking up a page of Content Items by their Model Id.
broadleaf.content.cache.by-item-and-model-uri: Caches results when looking up a Content Item by a combined Model and Item URI.
broadleaf.content.cache.all-items-by-model-id: Caches results when looking up Content Items by a Model’s Id.
broadleaf.content.cache.all-items-by-filter: Caches results when looking up Content Items with an RSQL filter.
broadleaf.content.cache.by-zone-name: Caches results when looking up a Content Zone by name.
These properties are for configuring the data source and are essentially the same as for any other service with a backing data store.
This exposes all of the Spring DataSourceProperties under broadleaf.content.datasource.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
This exposes all of the Spring LiquibaseProperties under broadleaf.content.liquibase.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
This exposes all of the Spring JpaProperties under broadleaf.content.jpa in addition to the Spring HibernateProperties under broadleaf.content.jpa.hibernate.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
These are additional properties that define datasource configuration that employs SchemaDelegatingDataSource. This allows through configuration alone a setup that declares multiple datasources (each tied to a schema) backed by a common base datasource. This config is generally employed as part of a flex-package installation where multiple services run together in a single JVM.
broadleaf.content.delegating.schema: The schema that borrowed connections should be initialized to in SchemaDelegatingDataSource.
broadleaf.content.delegating.delegateRef: The back-reference to another section of configuration that fully describes the base datasource backing the SchemaDelegatingDataSource.