Each content bean in the CAE represents a content object from the CoreMedia Content Server.
In order to specify the indexed content beans, you have to define the set of source contents using a content selector.
Configuring the Content Selector
The file caefeeder-triggers.xml located in classpath
/framework/spring/caefeeder/ contains the Spring Framework bean definition of
the content selector. The default implementation PathAndTypeContentSelector
selects contents by type and path. You can configure it with the following properties:
feeder.contentSelector.basePath- Specifies a comma-separated list of content repository folder paths.
-
feeder.contentSelector.contentTypes - Contains a comma-separated list of content types.
feeder.contentSelector.includeSubTypes- Specifies whether subtypes of the configured content types are selected as well. The default is true.
Example
Example 5.4, “ContentSelector example” selects all contents of type CMMedia,
CMArticle, CMDownload and CMCollection (including sub types) which are
located below the path /Sites:
feeder.contentSelector.basePath=/Sites feeder.contentSelector.contentTypes=CMMedia,CMArticle,CMDownload,CMCollection feeder.contentSelector.includeSubTypes=true
Example 5.4. ContentSelector example
Customizing the content types list
You can extend the set of indexed content beans by customizing a property of the content
selector called contentTypeNames. This is useful when you use
extensions (see the [CoreMedia DXP 8 Manual] for details),
because an extension can not extend a property file but it can extend Spring configuration.
The following example defines a simple
configuration which customizes the bean contentTypeNames, defined in file
caefeeder-triggers.xml, by adding a CMPicture to the set of
content types defined in feeder.contentSelector.contentTypes:
<customize:append id="contentTypeNamesCustomizer" bean="contentTypeNames">
<list>
<value>CMPicture</value>
</list>
</customize:append> |  |  |
 |