jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg" <stefan.guggisb...@day.com>
Subject Re: ??: Does mixin effect search result?
Date Mon, 16 Jun 2008 09:59:19 GMT
On Mon, Jun 16, 2008 at 10:47 AM, Marcel Reutegger
<marcel.reutegger@gmx.net> wrote:
> Alexander Klimetschek wrote:
>> 2008/6/16 Yonder <zyzha@yahoo.com.cn>:
>>> I'm weak in English, but afraid that mix is also allowed:
>>> mixin_opt ::= "mixin" | "mix" | "m"
>> Oh, sorry, you are right. Your cnd is valid. I was so used to line
>> breaks in node type definitions that I thought it is required ;-)
>> But the actual problem is the element() function: it only allows for
>> primary node types in the second argument, not for mixins. So the
>> query for the mixin ocm:file2 cannot find any node. See Section
>> "element() Node Test" in the JCR spec.
> looks like jackrabbit is not in line with the spec, because jackrabbit does
> consider mixin types in the element() node test.
> 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?

yes, it should. i just checked, currently it doesn't. i'll open a jira issue.


> regards
>  marcel

View raw message