Hi Wojtek, nice proposal : )
Indexing should include all available contributions. File names as well as their contents (except non readable files like Java classes) should be indexed. Every indexed item should have link to its contribution parent. I agree about a link to contributions...actually, if you make the contributions the main search target, I mean, if the contribution will be what the user would want as the results, every indexed term would point to a contribution, so it already has a link to the contribution : ) . I only disagree when you say that Java classes are non-readable, they are readable, they have class/method/variables/annotation names, even a .zip is readable, you could open it and index the name of the files contained in it, as well as the contents of this files, if readable. - Maybe we should consider candies like Ajax hints while typing search phrase? I would be reeeeally cool : ), but not priority. It could be easily added later after everything else is working : ) -- simply search for files by name I would recommend to index file names using an specific Lucene field for that, like "filename", so the query could be filename:(contributionname.composite)...otherwise, if the user types only contributionname.composite, it could look for this text in every field contained in the index, Lucene has a special feature for that, so it's easy to be implemented. Associating terms with a field is always good for fieltering :) Proposal: > preview link (if item is readable) If the item is not readable, a link could also be provided for downloading : ) Could you please provide to us a more detailed timeline? I think you should add more detailed about how the text will be parsed and indexed. The way you do this is very important because it implies in how the documents/contributions/artifacts can be searched and what kind o results can be provide to the user. Best Regards, Adriano Crestani On Tue, Mar 31, 2009 at 9:29 AM, Luciano Resende <[email protected]>wrote: > On Tue, Mar 31, 2009 at 9:21 AM, Wojtek Janiszewski > <[email protected]> wrote: > > Hi, Luciano, Raymond. > > > > Thanks for your input, I've just updated my proposal [1]. I've included > most > > of yours ideas, and I'll also work on possibility of integration with JMX > > management. > > > > Luciano, I have one comment: > > > > Luciano Resende: > >>> > >>> 1. Indexing > >>> > >>> - Indexing should include all available contributions. File names as > well > >>> as > >>> their contents (except non readable files like Java classes) should be > >>> indexed. Every indexed item should have link to its contribution > parent. > >>> > >>> - After adding, updating or deleting contribution from domain manager > web > >>> application appropriate items should be reindexed. > >>> > >>> - We may also consider having connections between indexed items, ie. we > >>> could scan composite files to acquire children names and build reversed > >>> links, so every indexed item (script, Java class etc.) could have > >>> connection > >>> to its composite parents. > >>> > >> > >> Looks good, I'll probably give first priority for Composites and other > >> SCA related files, WSDL and XSD. > >> > > > > I don't understand. Could you give more description? > > > > I was just trying to say that, if it makes any difference, we should > provide search for these types of artifacts first, them move to the > others. > > > > > > > [1] - > > > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Searching+artifacts+across+SCA+domain > > > > > > -- > Luciano Resende > Apache Tuscany, Apache PhotArk > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ >
