On 05.09.2006, at 22:17, Boris Kraft wrote:
If all else fails you can always by a Google appliance, I hear they are painless to setup and maintain. ;-)
Honestly this is not a bad advice. After all the user does not want to search the repository contents, but rather the HTML output that comes from the repository. As you all know there may be big differences between the two things, e.g.
- you have content in the repository that does not get displayed on the output page - your template gathers content from other sources and displays it on the page
In both cases searching the repository will not do much good. The search included in JCR is good for admins/editors dealing with the real repository content, or of course for custom search queries (i.e. searching certain fields underneath a certain path in the repository). When it comes to searching the HTML output, something like nutch (http://lucene.apache.org/nutch/) might be the better solution.
My 2 cts. -Will ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
