| 1 | <?xml version="1.0" encoding="UTF-8"?> |
|---|
| 2 | <!-- |
|---|
| 3 | Component Registry context.xml |
|---|
| 4 | Twan Goosen <twan.goosen@mpi.nl>, 21/9/2011 |
|---|
| 5 | |
|---|
| 6 | This file contains configuration options for the ComponentRegistry |
|---|
| 7 | package which includes both the REST service and the Flex UI. |
|---|
| 8 | |
|---|
| 9 | For information about the component registry, see |
|---|
| 10 | <http://www.clarin.eu/cmdi> and |
|---|
| 11 | <http://trac.clarin.eu/wiki/ComponentRegistry>. |
|---|
| 12 | |
|---|
| 13 | == DATABASE CONNECTION == |
|---|
| 14 | |
|---|
| 15 | By default, the application assumes a named (JNDI) datasource |
|---|
| 16 | jdbc/ComponentRegistry that provides access to the ComponentRegistry |
|---|
| 17 | database. |
|---|
| 18 | |
|---|
| 19 | For more information, or configuring a custom datasource Spring bean, |
|---|
| 20 | see WEB-INF/spring-config/datasource-jdbc.xml |
|---|
| 21 | |
|---|
| 22 | A database creation script can be found at |
|---|
| 23 | <http://svn.clarin.eu/ComponentRegistry/tags/ComponentRegistry-${project.version}/ComponentRegistry/src/main/sql/create.sql> |
|---|
| 24 | |
|---|
| 25 | == SPRING CONFIGURATION == |
|---|
| 26 | |
|---|
| 27 | This application uses the Spring framework <http://www.springsource.org/>, |
|---|
| 28 | version 2.5. Part of its configuration is handled through Spring beans. |
|---|
| 29 | These are defined in WEB-INF/applicationContext.xml and the files in |
|---|
| 30 | WEB-INF/spring-config. |
|---|
| 31 | |
|---|
| 32 | == SHIBBOLETH == |
|---|
| 33 | |
|---|
| 34 | This application uses Shibboleth authentication. Make sure that the URIs |
|---|
| 35 | for login/logout are set correctly in WEB-INF/shhaa.xml. |
|---|
| 36 | --> |
|---|
| 37 | <Context antiJARLocking="true" path="/ComponentRegistry"> |
|---|
| 38 | <!-- |
|---|
| 39 | Passed to the Flex via compRegConfig.jsp so that it can locate the |
|---|
| 40 | ComponentRegistry REST service. Just supply the PUBLIC application root |
|---|
| 41 | in the path; the '/rest/registry' part will be added by the application. |
|---|
| 42 | |
|---|
| 43 | "serviceUrlPath" is MANDATORY in all cases and should contain the path |
|---|
| 44 | of the application relative to the server root, starting with a forward |
|---|
| 45 | slash but no trailing slash, e.g. "/ComponentRegistry", or "" for root |
|---|
| 46 | deployment. |
|---|
| 47 | |
|---|
| 48 | In addition, either "serviceUrlPath" OR the two parameters |
|---|
| 49 | "serviceUrlProtocolHeader" and "serviceUrlHostHeader" need to be |
|---|
| 50 | defined. |
|---|
| 51 | --> |
|---|
| 52 | <Parameter name="eu.clarin.cmdi.componentregistry.serviceUrlBase" value="${serviceUrlBase}"/> |
|---|
| 53 | <Parameter name="eu.clarin.cmdi.componentregistry.serviceUrlPath" value="${serviceUrlPath}"/> |
|---|
| 54 | <!-- |
|---|
| 55 | Uncomment two lines below iff you would like to use the protocol and host |
|---|
| 56 | provided in the request headers. |
|---|
| 57 | <Parameter name="eu.clarin.cmdi.componentregistry.serviceUrlProtocolHeader" value="X-FORWARDED-PROTO"/> |
|---|
| 58 | <Parameter name="eu.clarin.cmdi.componentregistry.serviceUrlHostHeader" value="X-FORWARDED-HOST"/> |
|---|
| 59 | --> |
|---|
| 60 | |
|---|
| 61 | <!-- |
|---|
| 62 | Location that gets redirected to from /documentation.jsp, which in turn is linked to |
|---|
| 63 | from the Flex application through the 'Help' link button. |
|---|
| 64 | --> |
|---|
| 65 | <Parameter name="eu.clarin.cmdi.componentregistry.documentationUrl" value="http://www.clarin.eu/cmdi"/> |
|---|
| 66 | <!-- |
|---|
| 67 | Space-separated list of users (getRemoteUser()) that should have access to the admin area of the ComponentRegistry |
|---|
| 68 | --> |
|---|
| 69 | <Parameter name="eu.clarin.cmdi.componentregistry.adminUsers" value="twagoo@mpi.nl twan.goosen_mpi.nl@clarin.eu dietuyt@mpi.nl dietuyt_mpi.nl@clarin.eu menwin@mpi.nl menwin_mpi.nl@clarin.eu"/> |
|---|
| 70 | <!-- |
|---|
| 71 | Location of the CMDI general component schema that validates component specifications |
|---|
| 72 | --> |
|---|
| 73 | <Parameter name="eu.clarin.cmdi.componentregistry.generalComponentSchemaUrl" value="https://infra.clarin.eu/cmd/general-component-schema.xsd"/> |
|---|
| 74 | <!-- |
|---|
| 75 | Location of the stylesheet that transforms component specifications into XML schema documents |
|---|
| 76 | --> |
|---|
| 77 | <Parameter name="eu.clarin.cmdi.componentregistry.component2SchemaXslUrl" value="https://infra.clarin.eu/cmd/xslt/comp2schema-v2/comp2schema.xsl"/> |
|---|
| 78 | <!-- |
|---|
| 79 | Schema location that will go into xsi:schemaLocation attribute of component specification. Beware this should follow |
|---|
| 80 | XML standards and have a namespace component (URI) and schema location component (URL) separated by a space |
|---|
| 81 | --> |
|---|
| 82 | <Parameter name="eu.clarin.cmdi.componentregistry.componentSpecSchemaLocation" value="http://www.clarin.eu/cmd https://infra.clarin.eu/cmd/general-component-schema.xsd"/> |
|---|
| 83 | <!-- |
|---|
| 84 | Base location of the ISOcat service |
|---|
| 85 | --> |
|---|
| 86 | <Parameter name="eu.clarin.cmdi.componentregistry.ccrRestUrl" value="https://openskos.meertens.knaw.nl/ccr/api/"/> |
|---|
| 87 | </Context> |
|---|
