It is not only possible to define content type definitions in separate files but also in CoreMedia Application Plugins (Section 4.1.6, “Application Plugins” in Blueprint Developer Manual ).

Resources matching the pattern classpath*:framework/doctypes/**/*.xml will be picked up as document type definitions, which can contain new document types as well as document type aspects (see Section 4.2.3, “Attaching Properties to Existing Content Types”). The extended document type model becomes active on first Content Server start after the Plugin has been added.

Caution

If a Plugin comes with custom document type definitions, once you have activated it and started the Content Server, its database is adjusted accordingly. You must not disable the Plugin afterward, or the Content Server might refuse to start, because the additional document type definitions are missing. In case you want to remove such a Plugin, please consult Section 4.3, “Schema Update”.

Custom Grammar Support Unavailable

Providing a custom grammar via Plugin is not possible. Thus, you can only reference grammars via XmlGrammar or XmlSchema that are available at the classpath.