JavaServer Faces 2.2 is more evolutionary than it is revolutionary. This is by design as JSF 2.0 added a whole bunch of new features as part of the Java EE 6 platform. The Preface 1 from the JSF 2.2 Public Review specification provides a list of changes between JSF 2.1 and 2.2.

There’s a lot to love about JRuby. It performs better than just about any other implementation. It has solid, reliable, parallel threading. Its extensions are managed code and won’t segfault or interfere with threads or GC. And it gives Ruby access to anything that can run on a JVM, including code written in other languages.

RAM prices have plummeted and servers with tens or even hundreds of Gigabytes of memory have become common these days. What this means to your application’s architecture and deployment topology is important. On heap caching of data within enterprise application is a common example.

Eclipse 4 has reinvented itself by redefining its internal API and its capabilities. This session presents the new API of Eclipse 4.

This session will present a case study focusing on the development of a robust, horizontally scalable, enterprise CRM system at Dealer.com built primarily upon a Spring technology stack.

Learn several advanced deployment concepts and techniques on how to deploy your Java applications. Some of them were introduced recently, and others have been available for some time but are underutilized because they are perceived as hard to master.

JAX-RS 1.X has been a hugely successful Java API, and a lot of real-world experience has resulted in proposals of several new features. JSR 339 was created in early 2011, with the objective of exploring and scoping all these proposals.

Learn how you can use Eclipse’s quick-fix refactoring (and a little common sense) to restructure some hairy code into something rather more palatable.

The makefiles for the OpenJDK have begun to show their age. They were slow, did not allow for incremental builds, and created a high barrier of entry for new Java developers who wanted to join the OpenJDK development community.

One of the major themes of Java EE 7 and JPA 2.1 is multi-tenancy and EclipseLink, the JPA 2.1 reference implementation, has blazed the trail by shipping support for both multi-tenancy and tenant specific extensions in the Eclipse Indigo release. EclipseLink multi-tenancy enables the use of a single persistence unit by multiple tenants while keeping their data isolated and secure.