You might also want to take a look at [1] for indexing configuration understanding. You can define a per property analyzer as well, see [1] at the bottom,
-Ard [1] http://wiki.apache.org/jackrabbit/IndexingConfiguration > > Hi Paco, > > I think the Lucene analyzer used in your workspace and > defined in repository.xml does not tokenize string as you wanted. > Indeed, the default analyzer is Lucene StandardAnalyzer [1] > which used Lucene StandardTokenizer [2] which claims to: > "Splits words at punctuation characters, removing punctuation. > However, a dot that's not followed by whitespace is > considered part of a token." > > You can still use a custom analyzer by setting the class name > to use in the property "analyzer" of the SearchIndex element > in repository.xml. > > If the workspace is already created, you need to update > repository/workspaces/<workspaceName>/workspace.xml > and also delete the repository/workspaces/<workspaceName>/index > directory in order to reindex nodes at startup. > > [1] > http://lucene.apache.org/java/2_2_0/api/org/apache/lucene/anal > ysis/standard/StandardAnalyzer.html > [2] > http://lucene.apache.org/java/2_2_0/api/org/apache/lucene/anal > ysis/standard/StandardTokenizer.html > -- > Sébastien Launay > > Paco Avila a écrit : > > I've a property called "okm:name" where I store each > document name. If > > the document is called "hola mundo.txt" why the query > > > > /jcr:root//*[jcr:contains(@okm:name, 'hola')] > > > > return the document node but: > > > > /jcr:root//*[jcr:contains(@okm:name, 'mundo')] > > > > does not return anything? > > > > >
