2009/3/30 Wojtek Janiszewski <[email protected]>: > Hi, > I'm interested in taking part in Google Summer of Code and project > "tuscany-scadomain-search" [1] sounds interesting to me. > > I've made a quick look inside domain manager web app and Apache Lucene and > made few assumptions for a start. I defined three main areas which project > should cover and they are indexing, searching and presentation. Having those > areas separeted allows us to write modular code and test it. > > 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. > 2. Searching > > - Search feature would be accessible via SCA domain manager web application. Tuscany and it's various bindings make it easier to define a search component and expose it using various different protocols. While I agree that we should concentrate in producing a search ui integrated with the existent SCA domain manager web application UI (e.g using a json-rpc or other web 2.0 binding) but we should not prevent other scenarios to consume this search component. > It should allow to: > -- simply search for files by name > -- search files content > -- filter - search inside specified contribution or composite +1 with sca related files, wsdl and xsd having a high priority > > - Maybe we should consider candies like Ajax hints while typing search > phrase? > +1 Another think I had in mind was to allow user to search for component foo, and when displaying the result have all the references linked together (e.g if component foo has a <implementation.java class="fooImpl.java"> clicking fooImpl.java would just redirect you to the actual file content)... > - More research one Apache Lucene could provide more searching ideas. > Adriano Crestani is the Lucene expert ... he should be able to help here as well... > 3. Presentation > > - Each search result should be presented using name and link to contribution > which it belongs to. If it's viewable (it's not Java class etc) then simple > preview feature for such item should be enabled. Obviously matched text > should be highlighted (as Google does). > > - If information about composite parents for this items would be accessible > then such composites also should be listed. > > > This quick draft is direction which I'll take while creating proposal. It > appears to be interesting project, especially it allows to explore new areas > (everything beyond bindings in Tuscany, Lucene). There is still much place > to improve (like other features) so any comments are welcome. > > Thanks, > Wojtek > > [1] - > http://wiki.apache.org/general/SummerOfCode2009#tuscany-scadomain-search > -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
