On Mon, Jun 16, 2008 at 11:16 AM, Yonder <[EMAIL PROTECTED]> wrote:
>> there's something else that is strange. ocm:file2 is defined as a mixin, but
>> is
>> later used in the code as a primary type to create a node. shouldn't that be
>> prevented?
>
> It's no my invention. I'm using Jackrabbit OCM, its query implementation
> always element() for type constrain whether the node type is mixin or not:
No, he means this line in your code:
Node file2 = root.addNode("second", "ocm:file2");
The second parameter should be a primary type, not a mixin.
Regards,
Alex
--
Alexander Klimetschek
[EMAIL PROTECTED]
