Requirements

A CoreMedia deployment can host multiple sites which frequently differ in layout and functionality. It is a common requirement to use different view templates for those sites but still be able to define reused templates across sites flexibly.

Solution

The CoreMedia CAE offers a very flexible view selection mechanism by providing the ViewRepositoryNameProvider and ViewRepositoryProvider abstraction (see Section 4.3.3, “Views” in Content Application Developer Manual).

CoreMedia Blueprint offers the BlueprintViewRepositoryNameProvider implementation which for each lookup of model and view generates a list of view repository names to query. The list is created based on

This allows for more fine-grained control of the used view repositories as view repositories can be configured not only specific for a site but also for each site section.

CoreMedia Blueprint uses the standard CAE TemplateViewRepositoryProvider to create from the list of view repository names the list of actual view repositories to query. CoreMedia Blueprint configures the following templateLocationPatterns for the TemplateViewRepositoryProvider:

Example: For a content of the corporate site the BlueprintViewRepositoryNameProvider yields the view repository names "corporate". The TemplateViewRepositoryProvider would then return the following view repositories which are queried for the responsible view: