portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Spencer <paulspen...@mindspring.com>
Subject Re: [Proposal] Lucene Search Service
Date Thu, 22 May 2003 00:40:27 GMT
Mark,

What?

.xreg file contain descriptive information ABOUT a registry entires, 
like portlets. They do NOT contain portlet content.  If you want the a 
portlet's content searchable, then I suggest having the portlet add it's 
content to the search service, via the add method.

Paul Spencer

Mark Orciuch wrote:

>I fully support this proposal. One very important document handler that
>comes to mind is .xml (.xreg). To me, indexing portlet registry would be
>very important because that's where where the portal's content resides. I
>wouldn't mind getting involved in this task once we agree on the
>architecture.
>
>Best regards,
>
>Mark C. Orciuch
>Next Generation Solutions, Ltd.
>e-Mail: mark_orciuch@ngsltd.com
>web: http://www.ngsltd.com
>
>
>  
>
>>I've noticed the new LuceneSearchService and have been giving
>>some thought
>>as to how I might like to put it to use.  I'll admit to not
>>having that much
>>experience with Lucene, so if anyone thinks that this won't work,
>>just let
>>me know.
>>
>>In terms of the service, perhaps there should be a generic SearchService
>>interface of which the Lucene service is an implementation.  That way, if
>>there was some other great search engine someone wanted to use,
>>they could
>>swap it out.
>>
>>I was thinking that there could be 4 basic methods.  These would be
>>add(Object o), update(Object o), remove(Object o), and search(query).  In
>>order to support more than one object type, we could setup the service to
>>accept LuceneDocuement loaders, which would know how to turn the generic
>>object into a Lucene document that can be added to the index.  Here's an
>>outline.
>>
>>services.SearchService.classname=org.apache.jetspeed.services.sear
>>ch.lucene.LuceneSearchService
>>services.SearchService.index=WEB-INF/index
>>
>>services.SearchService.handler.name=ObjectXHandler
>>services.SearchService.handler.ObjectXHandler.classname=com.mycomp
>>any.lucene.ObjectXToDocument
>>services.SearchService.handler.ObjectXHandler.object_type=com.myco
>>mpany.ObjectX
>>
>>services.SearchService.handler.name=ObjectYHandler
>>services.SearchService.handler.ObjectYHandler.classname=com.mycomp
>>any.lucene.ObjectYToDocument
>>services.SearchService.handler.ObjectYHandler.object_type=com.myco
>>mpany.ObjectY
>>
>>So, when it comes time to add the object to the index, the
>>service looks up
>>the appropriate object handler, uses it to convert the object to a Lucene
>>document, and then adds/updates/removes it from the index.  In terms of
>>searching, this would allow all kinds of different indexed
>>documents to be
>>returned from a search.  Perhaps a filter could be placed in the
>>search so
>>that only certain types of documents that originally came from
>>certain types
>>of objects could be returned.
>>
>>Again, just an idea.  But it strikes me as a powerful one with
>>respect to a
>>general indexing solution.
>>
>>Jeremy Ford
>>
>>_________________________________________________________________
>>Protect your PC - get McAfee.com VirusScan Online
>>http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>>
>>
>>
>>
>>    
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
>  
>




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message