It's part of the node definition: [att:cmsFolder] > nt:base, mix:versionable, mix:deletable - att:nodeTypeKey (STRING) mandatory - * (UNDEFINED) multiple - * (UNDEFINED) + * (att:cmsContent) VERSION + * (att:cmsFolder) VERSION
[att:cmsContent] > nt:base, mix:versionable, mix:deletable - att:nodeTypeKey (STRING) mandatory - * (UNDEFINED) multiple - * (UNDEFINED) Thanks - -----Original Message----- From: Alexander Klimetschek [mailto:aklim...@adobe.com] Sent: Wednesday, January 05, 2011 10:52 AM To: users@jackrabbit.apache.org Subject: Re: problem with removeMixin On 05.01.11 16:35, "PALMER, THOMAS C (ATTCORP)" <tp3...@att.com> wrote: >ries to strip the mix-in when >promoting to the next workspace in the workflow. Just a guss: was the mixin added through Node.addMixin() (then it should work, if the version history is gone, afaik) or is it already part of the node's primary node type (then you can't remove a mixin from a certain node)? Regards, Alex -- Alexander Klimetschek Developer // Adobe (Day) // Berlin - Basel
