Ever go to compile a project and you get an unresolved dependency on some class and you have no idea where it came from? If there was some way to find out what jar the class is in... Well now, there is: www.jarhoo.com. In many cases, you can tell right away what jar you'd need to fix a broken dependency. (Not too many jars have org.jdom classes in them.) But for some cases, especially beginners, figuring out which jar you need to add your classpath can be a daunting, frustrating task.

Jarhoo.com helps find those missing jars. The one downside to jarhoo is sheer number of possible jars. For example, a search for "EntityBean" returns dozens of jars. In practice, however, you'd use something like "javax.ejb.EntityBean" but even that search string returns at least two dozen options. Granted, that still makes it a bit easier at least knowing some options. Another problem is that the site appears to list every version of the jar in its system so you could end up with hits leading to old, outdated jars.

But overall a nice tool to have.

For those of you looking for documentation for JasperReports that covers all the goodies added lately, 2.0 of the Ultimate Guide is out. It looks like the price has gone up, but it seems to cover a lot of ground. It's definitely worth it if you're new to JR. Details can be found here.

I have a client who is in need of some people to help with their applications. Travel is 100% to sites are all over the country. Travel would be with Mon-Thurs or Tue-Friday depending on the exact client. They are looking for folks with J2EE skills (servlets, jsps, etc.) Actual work will vary by project. Projects should typically be 3-6 months. Expenses are included though the means of recouping those expenses will vary by client as well. Training for new team members is scheduled to start on 8/22. The rate is $50/hour.