Thanks for checking it out! My implementation is pretty simple. Building the index, I only look at <META NAME="keywords" ...> elements from the generated HTML, which conveniently contains all class/interface names, as well as methods and constants. The last two I'm currently indexing, but not yet searching, mostly because it adds a lot to the results, and I couldn't quite convince myself that I'd really use a method lookup (but, if you do break on case shifts, it might be more useful).
Each document contains the classname, the fqcn, and package name. So I just construct a BooleanQuery across all three with the user's input (appending *), then sort the results by the shortest match. I do like the idea of breaking on case, this would be especially great for finding interface implementations (searching for readers and writers, e.g.). -l -----Original Message----- From: Erik Hatcher [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 01, 2006 7:16 PM To: java-user@lucene.apache.org Subject: Re: javadoc lookup Nice! I'm curious, what do you have cooking on the server-side? Having Lucene showing terms from an index of javadocs would allow for partial matches such that QueryParser pops ups if someone types "parser" (provided the text was tokenized at case shifts). Erik On Mar 1, 2006, at 6:23 PM, Larry Ogrodnek wrote: > Hey, I put together a little ajax / lucene javadoc lookup site that I > just wanted to share.... I've found it pretty useful to be able to > just > type a few letters instead of navigating through the standard javadoc > frames... > > > > http://jdk.representqueens.com:9090/s/jdk/ > > http://jdk.representqueens.com:9090/s/lucene/ > > > > > > thanks, > > l > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
