Hi, Simon, comments inline. Thanks, Wojtek
Simon Laws:
Hi Wojtek Nice proposal (and something that would be really useful for Tuscany). A question. It feels like absolutely the right thing to do to start at the contribution and contribution content level but I'm interested in the index field you have described as "Service/Reference/Component/Binding/Implementation/... " which to me suggests some indexing of the contents of the files in the contribution, in this case the composite file.
By "Service/Reference/Component/Binding/Implementation/... " field I meant multiple fields. In fact we would have separate field for service, reference, component etc.
I'm asking as I'm attracted by the presentation example you give where you show an initial phrase search giving way to more targeted item based searches. A complexity of Tuscany is that it's based on number hierarchies and relationships, e.g. contribution import/export component type component promotion component wiring domain/node confguration intent and policy configuration Finding things can often mean searching through various, seemingly unrelated, files. This is particularly the case where policy is concerned. It seems that you are solving this problem and I'm wondering what general provision can be made to extend the index beyond the original contribution object. Regards Simon
I'm not sure if I'm getting you correctly. Do you mean having some general index field instead of multiple fields for Service, Reference, Component etc.?
