root/org.nuxeo.ecm.core/trunk/nuxeo-core-schema/src/main/resources/OSGI-INF/SchemaService.xml

<?xml version="1.0"?>

<component name="org.nuxeo.ecm.core.schema.TypeService"
  version="1.0.0">
  <documentation>
    Manage document types and schemas.
    Allows registrering new types defined using XSD schemas
    @author Bogdan Stefanescu (bs@nuxeo.com)
  </documentation>

  <service>
    <provide
      interface="org.nuxeo.ecm.core.schema.SchemaManager"/>
  </service>

  <implementation class="org.nuxeo.ecm.core.schema.TypeService" />

  <extension-point name="configuration">

    <documentation>
      Type manager configuration
      <p>
      This includes prefetching options and other global configuration regarding type management
      </p>
    </documentation>

    <object
      class="org.nuxeo.ecm.core.schema.TypeConfiguration" />
  </extension-point>

  <extension-point name="doctype">

    <documentation>
      Extension Point to register new document types.
      <p/>
      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.
      <p/>
      A doctype XML extension may contain several 'doctype' elements.
      A doctype element may look like this:

      <pre>
        <doctype name="File" extends="Document">
          <schema name="common" />
          <schema name="file" />
          <schema name="dublincore" />
          <schema name="uid" />
          <facet name="Downloadable" />
          <facet name="Versionable" />
        </doctype>
      </pre>
    </documentation>

    <object
      class="org.nuxeo.ecm.core.schema.DocumentTypeDescriptor" />
  </extension-point>

  <extension-point name="schema">

    <documentation>
      Extension Point to register new schemas.
      <p/>
      Schemas are defined using XSD files.
      The schema extension XML may containg  several 'schema' objects as
      the following ones:
      <pre>
        <schema name="common" src="schema/common.xsd" />
        <schema name="dublincore" prefix="dc" src="schema/dublincore.xsd" />
      </pre>
      The <i>name</i> attribute uniquely identify the schema, the <i>src</i> attribute specify
      the path to that schema (relative to the bundle root) and the <i>prefix</i> is used as
      a prefix (short name) of the schema namespace.
      The schema namespace is the targetNamespace defined inside the XSD file
      <p/>
      Note that multiple schemas can share the same target namespace and prefix
    </documentation>

    <object
      class="org.nuxeo.ecm.core.schema.SchemaBindingDescriptor" />
  </extension-point>

  <extension-point name="typeHelpers">
    <documentation>
      This extension point let you contribute new type helpers that control extended
      type handling like encondig, decodig values etc.
      <p/>
      A contribution example:
      <pre>
        <helper schema="file" type="content" class="BlobHelper"/>
      </pre>
    </documentation>
    <object class="org.nuxeo.ecm.core.schema.TypeHelperDescriptor" />
  </extension-point>


  <extension-point name="provider">
    <documentation>
    Extension point to register type providers. Type providsers are usually used to import types
    defined on remote servers
    </documentation>
    <object class="org.nuxeo.ecm.core.schema.TypeProviderDescriptor"/>
  </extension-point>

</component>