Workspace Configuration

Introduction

The Workspace element in therepository.xml is used as a template for separate workspace configuration files created for each new workspace. Because of this theWorkspace element is not interpreted directly from the repository configuration file. Instead the workspace configuration template is first copied into the workspace configuration file which is then interpreted to set up the configured workspace components. Thus modifying the workspace configuration template in the repository configuration file willnot affect existing workspace configurations.

An example Jackrabbit workspace configuration can be found in the Jackrabbit documentation. Hippo Repository has a custom workspace configuration for enablingfast faceted navigation through custom indexing. The main differences with a default Jackrabbit workspace configuration are theSearchIndex class andindexingConfigurationClass. SeeSearch Index configuration for explanation of all<SearchIndex> parameters.
Sample

The minimal Hippo Repository workspace configuration looks like:

<Workspace name="${wsp.name}">  <FileSystem>    <param name="path" value="${wsp.home}"/>  </FileSystem>  <PersistenceManager>    <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>    <param name="schemaObjectPrefix" value="${wsp.name}_"/>  </PersistenceManager>  <SearchIndex>    <param name="indexingConfiguration" value="indexing_configuration.xml"/>    <param name="indexingConfigurationClass" value="org.hippoecm.repository.query.lucene.ServicingIndexingConfigurationImpl"/>  </SearchIndex></Workspace>