2. Overview

The overall goal of the CoreMedia CAE (CAE) framework is to provide a structure for any kind of web application that accesses the CoreMedia content repository. The declarative nature of this framework and the independence of the layers ensure fast development and maintainable application design. You may also encounter the term "ObjectServer" throughout APIs or configuration files. Please read CoreMedia CAE in that case. The overall application setup and web request processing are handled by the Spring framework, so it is useful to have a solid knowledge of Spring before developing CAE applications.

To represent the content objects in the repository, Java objects called content beans can be generated that directly reflect the repository structure. It is possible to extend these generated beans with any kind of custom business logic.

On top of this data access object layer, a caching layer can be defined by simply declaring the cacheable properties of the content beans. The elements of the caching layer are views on the content beans and are therefore called data views.

Based on the types of the content beans and/or data views, suitable views are chosen in order to render the backend information. The object-oriented nature of the view registration and mapping subsystem harnesses the full power of inheritance and implementation relationships. Views may be defined in a supported template language, such as JavaServer Pages or FreeMarker, or in Java code.

The modular design makes it possible to extend and modify the CAE framework.

Caution

Support for JavaServer Pages (JSPs) is deprecated and will be removed in future releases.