jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From majohnst <m...@lattaoutdoors.com>
Subject Re: OCM Annotations constraint error
Date Fri, 14 Nov 2008 19:08:59 GMT

I am using the spring OCM classes in the jackrabbit sandbox and the
OCM-1.6-SNAPSHOT. My custom_nodetypes.xml did have the field named as
ocm:classname, but changing that to ocm_classname didn't work. Digging in a
little bit, in the JackrabbitSessionFactory bean when the
custom_nodetypes.xml and namespaces are trying to be loaded, it seems that
the "ocm" namespace has already been loaded from somewhere else. When the
JackRabbitSessionFactory tries to register the "ocm" namespace, it already
exists in the namespace registry.  What else would be registering the


Christophe Lombart wrote:
> If the namespace is well created in the repo, it is also possible to have
> a
> mistake in the property name defined in the mixin type ocm:discriminator.
> From 1.5, the name of the property has been changed into ocm_classname.
> Here
> is a example :
> <nodeType name="ocm:discriminator" isMixin="true">
>     <supertypes>
>       <supertype>nt:base</supertype>
>     </supertypes>
>     <propertyDefinition name="ocm_classname" requiredType="String"
> autoCreated="false" mandatory="true" onParentVersion="COPY"
> protected="false" multiple="false" />
>   </nodeType>
> Let me know if you need more help.
View this message in context: http://www.nabble.com/OCM-Annotations-constraint-error-tp20493710p20506649.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message