Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-14049

Allow setting perDocumentQuery=false through type service

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.9.3
    • Component/s: Core, Core VCS
    • Tags:
    • Impact type:
      Configuration Change
    • Upgrade notes:
      Hide

      Instead of setting it through the repository reconfig, it's now possible (and recommended) to specify in the facet definition using the type service that a query on the facet (NXQL: ecm:mixinType = ...) will never need to match per-document facets.

      So instead of, in default-repository-config.xml, having:

      <neverPerDocumentFacets>
      <facet>SomeFacet</facet>
      <facet>OtherFacet</facet>
      </neverPerDocumentFacets>

      You should use in the extension point defining the facet:

      <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype">
      <facet name="SomeFacet" perDocumentQuery="false"/>
      <facet name="OtherFacet" perDocumentQuery="false">
      <schema name="someschema"/>
      </facet>
      </extension>

      Show
      Instead of setting it through the repository reconfig, it's now possible (and recommended) to specify in the facet definition using the type service that a query on the facet (NXQL: ecm:mixinType = ...) will never need to match per-document facets. So instead of, in default-repository-config.xml, having: <neverPerDocumentFacets> <facet>SomeFacet</facet> <facet>OtherFacet</facet> </neverPerDocumentFacets> You should use in the extension point defining the facet: <extension target="org.nuxeo.ecm.core.schema.TypeService" point="doctype"> <facet name="SomeFacet" perDocumentQuery="false"/> <facet name="OtherFacet" perDocumentQuery="false"> <schema name="someschema"/> </facet> </extension>

      Description

      Currently neverPerInstanceMixins has to be specified in the repository configuration.

      This is not ideal because this is actually tied to the types, and we should be able to contribute new ones from a bundle without overriding a specific repository (whose name can change).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: