Rather than keep going with the dog-fight, why not putting down the exact requirements/usecase for this module (papaki), or is this already discussed elsewhere? I admit I don't know the details, but my personal preference would be for something really simple and really fast with minimal dependencies. Then users of the api/service do what they want with the information. And I wouldn't count too much on pre-propressing steps, that would be a nice option, but IMHO it has to be fast without pre-indexing. Now if there is overlap with existing functionality or there are things we can re-use, that's fine, but again the first thing is to be clear on what we want to achieve, rather than trying to fit the usecase into existing APIs that maybe not designed for that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261899#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...