On Wed, 2007-01-17 at 09:36 +0000, Luis Neves wrote: > Hi, > > Thorsten Scherler wrote: > > On Mon, 2007-01-15 at 13:42 +0000, Luis Neves wrote: > > > > > I think you should explain your use case a wee bit more. > > > >>>> What I do now to index XML documents it's to use a Filter to strip > > the markup, > >>>> this works but it's impossible to know where in the document is the > >>>> match located. > > > > why do you need to know where? > > Poorly phrased from my part. Ideally I want to apply "lucene filters" to the > xml > content. > Something like what Nux does: > <http://dsd.lbl.gov/nux/api/nux/xom/pool/FullTextUtil.html> >
http://dsd.lbl.gov/nux/#Google-like realtime fulltext search via Apache Lucene engine If you have a look at this you will see that the lucene search is plain and not xquery based. It is more that you can define relations like in SQL connecting tow tables via keys. Like I understand it, it will return the docs that have the xpath /books/book[author="James" and the lucene:match(abstract, $query) where the lucene match is based on a normal lucene query. I reckon it should be very easy to do something like this in a client environment like cocoon/forrest. See the nux code for getting an idea. If I would need to solve this I would look for a component that allows me XQuery like nux and a component that let me do query against a solr server. Then you "just" need to match the documents that return for both components a result with a custom method. salu2 > > -- > Luis Neves
