jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonder <zy...@yahoo.com.cn>
Subject Reply: Does mixin effect search result?
Date Mon, 16 Jun 2008 07:42:17 GMT
Thank you for your help. > This is not correct. A mixin is defined by stating "mixin" below
> first line of the node defintion. The ">" must be followed by a
> comma-separated of node and/or mixin super types.
> See the documentation on the Jackrabbit website for more information:
> http://jackrabbit.apache.org/node-type-notation.html

I'm weak in English, but afraid that mix is also allowed:

mixin_opt ::= "mixin" | "mix" | "m"

there is a example in the document:

[ns:NodeType]>ns:ParentType1, ns:ParentType2 o m
-ex:property='default1','default2' ! m a p * version
 <'constraint1', 'constraint2'
 m a p *  versionI can compile and run the SearchTest without any errors. Though I modified
test.cnd, the search result is same:
  Nodes ocm:file1 Found! 
  Nodes ocm:file2 not exist

I think there must be any other reasons.

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message