CoreMedia Studio uses a web application for delivering both static content (like the JavaScript code defining the application) and dynamic content stored in the CMS.
Dynamic content is provided by means of a REST service embedded in a Spring web application context. See http://www.springsource.org/ for details about the Spring framework. In the following section, it is assumed that you know about the essential concepts of the Spring inversion of control (IoC) container.
You can extend and modify the application context by providing additional configuration files
in the classpath. Such files must be named according to the pattern
component-*.xml and they must be put into the directory
META-INF/coremedia. It is recommended that the variable part of the file name is
equivalent to the name of the Maven module in which you define the XML file and optionally
Java classes required for your extension.
You must modify the application context to configure your content validation setup. See Section 7.15.1, “Validators” for the details.
 |  |  |
 |