Have you ever found yourself frustrated with a ClassNotFoundException? Would you like to know what libraries are in your project and what they depend on? Would you like to get a full report on this stuff every time you run your ant build? If so you need to take a look at the new JBoss Tattletale project!
The revised Public Review Draft of Contexts and Dependency Injection (JSR-299, the spec formerly known as Web Beans) was approved by the EC with all EC members voting Yes, except for Nortel and SpringSource who did not vote.
The first part of my new article, published today on JSFCentral, explains how you can increase the rendering performance of a data-driven, JSF-based Seam application by two orders of magnitude! The article originated out of a contract job I did over the summer (before joining Red Hat). I worked for a group of scientists to develop a data-driven application using Seam, JSF, and RichFaces. That means it comes straight to you from the real-world ;)
Many things in Eclipse require or uses a classpath, i.e. java projects,
junit and server launches, hibernate console etc. For these classpath containers are handy to use
instead of forcing users to individually pick the (possible long) list
of jars needed to get their work done. A classpath container allow plugin providers to automatically
create a group of jar's which can be added and removed in one operation - simple and efficient.