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.
I'm pleased to announce the release of Web Beans 1.0.0.ALPHA2. This release implements around 80% of the JSR-299, Java Contexts and Dependency Injection specification and represents the second major milestone on the road towards the GA release. The only major features missing from this release are conversations (already on their way!) and support for annotating your beans using XML.
Every JSF component has some specific attribute set unique for it. At the same time, almost all UI components have attributes that are common for all of them. For example, onclick, ondblclick, onblur, onmouseover, onmouseout, onmousedown and so on. They are named PassThru because they are rendered one-to-one to the final html layout.