loading table of contents...

4.1. Content Beans - Mapping content to objects

The CoreMedia CAE defines a mapping framework to create application-specific "business" objects from generic content objects. In order to do that, application specific classes have to be written and they have to be registered with a factory that is used throughout the application whenever a content object needs to be converted into an application bean. 

You do not need to write the beans from scratch. The CoreMedia CAE comes with a source code generator that reads your document type definition file and generates beans for each document type. The bean interfaces mirror the document properties, and the class hierarchy mirrors the document type hierarchy. After generating the code, you can modify and adapt it to your application’s needs.

  • ContentBeans can be used for other purposes than rendering, for example for implementing web services, for business logic deployed in the workflow server or in the CAE Feeder, or for custom standalone applications.

  • ContentBeans can be cached in DavaViews. See Section 4.2, “Data Views” for details.

  • ContentBeans are rendered by the rendering layer. See Section 4.3.3, “Views” for details.