[opencms-dev] Customise search ERROR [OpenCMS 6.0] (resend)

[David]

Hi Andras,
 Thank you for your suggestion which I think will work as an alternative.
However I would still very interested in finding out why the other approach 
does not work. Knowing this will help better understand how the OpenCMS 
Search API works which will come in handy should we need to customise it in 
the future for other applications. This type of code is fairly 
straight-forward with the original Lucene API itself. Only because OpenCMS 
API hides this interface details from us.
 The error just seems weird to me. 
 Thanks again for your help.
 Rgds,
David.

 On 7/29/05, Andras Balogh <abalogh at gmail.com> wrote: 
> 
> Hello David,
> 
> Have You considered using another approach? A solution would be to use a
> global search each time and filter out
> the results based on the list of files you have at runtime. It would
> require some work since the paging functionality will
> not work but i think it might work better than what you are trying to
> achieve now.
> I have never tested it but i have a feeling creating indexes "on the
> fly" for each site user search it will be an overkill.
> 
> Best regards,
> Andras.
> 
> David wrote:
> 
> > Hi,
> >
> > I am trying to customise the search behaviour in OpenCMS such that to
> > allow an application to dynamically create a new index source and
> > search index from an arbitrary set of files in VFS and perform a
> > search on those files. The code that I am using is given below. When I
> > run this from a JSP page it returned with an error saying /No analyzer
> > found for language "null". /The trace log for this error is given at
> > the bottom which points to method getAnalyzer() in CmsSearchManager.
> > So I checked the source code of this method and it looks perfectly
> > normal given that I already set the locale for my CmsSearchIndex
> > object to 'en'. I even test printing out the analyzer class name (see
> > code) using getAnalyzers() method of the CmsSearchManager to make sure
> > that analyzer for 'en' locale exists.
> >
> > So the analyzer is there and the locale has been set for the
> > CmsSearchIndex object, why does it still complain about the analyzer
> > being not found and weird enough in the error message it seems not
> > able to detect the locale ("null" value)? Has anyone experienced this
> > before and perhaps could provide some insights? Thanks very much for
> > your prompt response.
> >
> > Rgds,
> > David.
> >
> 
> 
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
> 



-- 
Rgds,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20050729/37fa6e53/attachment.htm>