In order for the CoreMedia CAE to instantiate the right classes at runtime, they need to be configured with the factory. The engine's default factory implementation uses the Spring application context to instantiate content beans. This way content beans can participate in Spring's dependency injection mechanism - for example, they can receive references to other services without having to resort to service lookups in JNDI or the servlet context.
The content type to content beans mapping is defined using Spring’s XML notation. It should contain a prototype definition for each class corresponding to a document type.
Prototype definitions follow a specific naming scheme. In order to be found by the
factory, they must be given the same name as the factory, followed by a colon ‘:’ and
the name of the document type for which they were generated. For example, a class
com.company.Article that represents Article documents is registered with the
factory as follows:
<bean name="contentBeanFactory:Article" parent="abstractContentBean" scope="prototype" class="com.company.ArticleImpl "/>
This line is a template for the content bean factory; it says:
This is a definition for a content factory bean for the document type Article
The bean might inherit configuration settings from a parent bean. This can simplify the configuration but is not mandatory.
This definition is a prototype, not a singleton, it must be newly instantiated for every article document
The implementation class is
com.company.ArticleImpl
In short this reads as: "for documents of type Article, return a
new instance
of
class com.company.ArticleImpl".
![[Note]](../common/images/note.png) | Note |
|---|---|
Important:
using
|
 |  |  |
 |