Re: [xwiki-devs] The problem with the rest services for autosuggestion.

Hi James, I agree with Marius that you should reuse as much as possible what already exists instead of creating an alternate service that does, in a great proportions, the same as an existing one but has one extra feature. So, as I was browsing trough REST's resources, I noticed an undocumented "/wikis/{wikiName}/attachments" [1] resource at the wiki level that is able to search for attachments. As you can see from the method's signature, it accepts parameters to filter your search by attachment name, page, space, author, and type. I will fix the REST API documentation and include it. This resource should do the trick for what you need, used in conjunction with the search resource that should handle documents. The advantage of this is that you can get json, as you did for the search resource. The disadvantage of the whole REST API, for your needs, might be that it is limited at wiki level and can not perform a multi-wiki search in one query (wihout you having to do a search for each wiki). On the other side, the Lucene search does not have this problem because it indexes all the wikis and can perform searches on all wikis in one query and it does it much faster than REST (which uses database queries). Also, lucene is used in the search suggest (the one at the top-right corner of the screen) and in the main XWiki search as well, so it would be much better if the results were consistent. Besides this, if the lucene system is improved over time, your results will also be improved as a result. So my suggestion is that you modify XWiki.SuggestLuceneService and make it accept a "media" parameter (or something similar) that should accept at least 2 values: "xml"(default) and "json". Based on this value, you can wrap the results of the lucene search into a basic json structure that you can easily use in your suggest box. You can check [2][3] and [4] for references of how to use Lucene search in XWiki. Once you are done with it, you can even do a pull request so that this feature gets integrated into XWiki. The best and cleanest solution would be that the REST search resource used internally lucene instead of a custom database query and that there would be a single search back-end (preferably configurable in administration). Anyway, it's not your job to fix XWiki :) so making XWiki.SuggestLuceneService return json too is the best way to go right now, IMO. Thanks, Eduard ----------------- References: [1] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… [2] http://extensions.xwiki.org/xwiki/bin/view/Extension/Lucene+Plugin [3] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… [4] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… On Tue, Jul 19, 2011 at 8:36 AM, 许凌志(Jamesxu)&lt;lingzhixu326(a)gmail.com suggestion current current user with types retrieved I http://localhost:8080/xwiki/bin/get/XWiki/SuggestLuceneService?outputSyntax… < http://localhost:8080/xwiki/bin/get/XWiki/SuggestLuceneService?outputSyntax… also _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs