Hi Phillipe, Next step is to define how the user will use the Search component to execute the search query and what will be returned to the user. It may return Lucene Document objects, which are the raw results of a Lucene query. Or it may return more specific objects, which represent all the domain artifacts included in the results, containing all the relationships, text highlighting, etc. I prefer the second option, this way the Search component users will not need to know how to deal with Lucene Document objects.
Yes, I agree it's not cool to return Lucene Document objects to the component user. It might also return too much info, mainly if you store the documents on the Document object, this way you will slow down the communication between the component and the user. So, lets keep it simple and only return the necessary information ; ) Best Regards, Adriano Crestani Campos On Thu, Jun 4, 2009 at 10:05 PM, Phillipe Ramalho < [email protected]> wrote: > Hi, > I was finally able to figure out how to add the new domain search project > to the maven and make it dependent of lucene-core library. It seems to be > working fine, so I created a patch and attached it to JIRA TUSCANY-2552 [1]. > The code is not integrated to domain manager yet, there is a lot of work > remaining yet, I will send more patches along my progress. > > Phillipe Ramalho > > [1] - http://issues.apache.org/jira/browse/TUSCANY-2552 > > > On Sun, May 31, 2009 at 1:28 AM, Phillipe Ramalho < > [email protected]> wrote: > >> Hi, >> These last weeks I have set my dev environment up and started coding some >> indexing code. >> >> My first challenge was to figure out what the user will provide the data >> about the SCA Domain to the Search component, so the Search component can >> analyze this data and index the relevant information. After some research >> and help from Luciano and Adriano I think the best way to collect this >> information is from a Contribution object. >> >> I already did some coding that introspect a Contribution object and >> extract the necessary information like components and their references and >> services, composites, contribution files, etc. Each one is indexed as a >> different document in the Lucene index. >> >> Next step is to define how the user will use the Search component to >> execute the search query and what will be returned to the user. It may >> return Lucene Document objects, which are the raw results of a Lucene query. >> Or it may return more specific objects, which represent all the domain >> artifacts included in the results, containing all the relationships, text >> highlighting, etc. I prefer the second option, this way the Search component >> users will not need to know how to deal with Lucene Document objects. >> >> I'm intending to send the first patch as soon as possible, I just need to >> integrate the new Search component module with maven. >> >> Regards, >> Phillipe Ramalho >> > > > > -- > Phillipe Ramalho >
