Wednesday Apr 13, 2011

Marching towards a Java EE 7 fullhouse of JSRs - CDI 1.1 & EJB 3.2

You might have missed (I did) the filling of the EJB 3.2 JSR last week. This is the follow up to Linda's "EJB.next" entry posted last month. In addition to the multi-tenancy cloud requirements, factoring out transactions in a similar way interceptors became a standalone specification is one of the interesting goals of this work.

Just yesterday JBoss/RedHat has also submitted JSR 346, aka CDI 1.1 and Pete "CDI/Weld" Muir has a blog with further details. We're looking here mainly at an incremental release with improvement such as allowing the built in implementation of the conversation context to be used outside of JSF (full list). Pete is calling for expert group members, if you are interested the link to apply is on the JSR page.

ALT DESCR
ALT DESCR

With each submission, a two-week voting period by the JCP Executive Committee starts. This means that the EJB 3.2 results will be available this coming Monday (April 18th) and the CDI 1.1 results a week later on the the 25th.

In the meantime, on the CDI side you should probably give this recent "Contexts and Dependency Injection in Java EE 6" article a read and make sure you're well aware of what Java EE 6 and CDI have to offer today.

Friday Jan 19, 2007

JSF RI Recent Improvements - Performance and Resource Injection

Bullet Shockwave

The JSF RI team - part of GlassFish - (RI home) has been improving continuously the functionality and performance of the implementation.

On the performance side, Ryan reports on measurements of tps under client (state is kept in the HTML sent to the client) and server (state is kept in the server memory) mode and both cases show very nice improvements, specially when using multiple processors. The best description I found on the tradeoffs between client and server modes is this blog by Jacob; as a simplification, server is faster while client uses less memory.

Another recent improvement is the Enhanced support for Resource Injection, which used to be applicable only to GlassFish but now can also be used in Jetty and Apache.

More entries related to JSF can be found here.

Added: Also see this Section in the GlassFish Wiki.