Custom versioning problem

[elgringo116_]

Hello,

For my graduation project I have to customise Nuxeo. To begin I did a plugin with my companyintern project lifecycle (It's works fine). But when I try to do a version management it does nothing, I use this xml :

<?xml version="1.0"?>
<component name="fr.société.nuxeo.versioning.contrib">
<service>
<provide interface="org.nuxeo.ecm.core.versioning.VersioningService" />
</service>
<implementation class="org.nuxeo.ecm.core.versioning.VersioningComponent" />
<extension-point name="versioningService">
<object class="org.nuxeo.ecm.core.versioning.VersioningServiceDescriptor " />
</extension-point>
<extension-point name="versioningRules">
<code>
<defaultVersioningRule>
<initialState major="1" minor="0" />
<options lifeCycleState="*">
<none />
<minor />
<major default="true" />
</options>
</defaultVersioningRule>
<versioningRule typeName="File" enabled="true">
<initialState major="1" minor="1" />
<options lifeCycleState="*">
<none />
<minor default="true" />
<major />
</options>
</versioningRule>
</code>
<object class="org.nuxeo.ecm.core.versioning.VersioningRuleDescriptor " />
<object
class=" org.nuxeo.ecm.core.versioning.DefaultVersioningRuleDescripto r " />
</extension-point>
</component>

Somebody can help me, please,I don't understand how this xml don't have any consequence in Nuxeo.

Sorry for my bad english and thank you for your advice.

[Florent_Guillau · Accepted solution]

This XML redefines a service, its implementation, its available extension points. You don't want to do all that. Just do a contribution to the extension point you're interested in.

[elgringo116_]

Thank for your answer,

[Florent_Guillau]

The documentation you mention is about an internal Nuxeo-defined service. You're confusing defining a service versus using it.