Nuxeo 5

Nuxeo 5 Component
org.nuxeo.ecm.core.schema.TypeService

Individual Documentation Coverage

done proportion
100.0 %


Manage document types and schemas.
Allows registrering new types defined using XSD schemas



Author: Bogdan Stefanescu ([email protected])

Version: missing

Location: nuxeo-core/nuxeo-core-schema/src/main/resources/OSGI-INF/SchemaService.xml

Require

No requirements

Required by

Implementation


Extension Points:

configuration


Type manager configuration.

For now this contains default prefetch options. For example:

        <configuration>
          <prefetch>common.icon, dc:title, dc:modified, dc:contributors, dc:creator</prefetch>
        </configuration>
      




doctype


Extension Point to register new document types.

Document types may implement several schemas and extends other
document types. You can compare document types with java
classes and schemas with java interfaces. Document types may
also contains several facets that define a behavior.

The prefetch element defines what fields are synchronously
indexed, and are made available in search results listings.

A doctype XML extension may contain several 'doctype' elements.
A doctype element may look like this:

        <doctype extends="Document" name="File">
          <schema name="common" />
          <schema name="file" />
          <schema name="dublincore" />
          <schema name="uid" />
          <facet name="Downloadable" />
          <facet name="Versionable" />
          <prefetch>dc:title, dc:modified, uid.uid</prefetch>
        </doctype>
      




schema


Extension Point to register new schemas.

Schemas are defined using XSD files.
The schema extension XML may containg several 'schema' objects as
the following ones:

        <schema name="common" src="schema/common.xsd" />
        <schema name="dublincore" prefix="dc" src="schema/dublincore.xsd" />
      


The name attribute uniquely identify the schema, the src attribute specify
the path to that schema (relative to the bundle root) and the prefix is used as
a prefix (short name) of the schema namespace.
The schema namespace is the targetNamespace defined inside the XSD file

Note that multiple schemas can share the same target namespace and prefix


typeHelpers


This extension point let you contribute new type helpers that control extended
type handling like encondig, decodig values etc.

A contribution example:

        <helper class="BlobHelper" schema="file" type="content" />
      



provider


Extension point to register type providers. Type providsers are usually used to import types
defined on remote servers


Has contribution from:

Last generation: 18:21:25 CEST 11/07/2009