EJB 3.1 Passes!
Nov 14th, 2008 Posted in Java | no comment »With EJB 3.0 being such an evolutionary step over EJB 2, the spit and polish has really been applied in the form of JSR #318, better known as EJB 3.1.
Gone are the requirements for EJBs to be packaged within EAR files: put them right in the WAR baby! And while you’re at it, dump the EJB deployment descriptor as well. Gone are mandatory interfaces for entities, POJOs for everyone. Added are brand new Timer and Scheduler services with callbacks and transaction support. No longer must we rely on MDBs for our asynchronous method needs: Now we simply annotate @Asynchronous to any session bean method with a return type of void or Future. JPA now includes support for inheritance and polymorphism. The addition of Java EE Profiles - especially the new Java EE Web Profile and EJB Lite.
The new specification is looking lean and mean. As someone who used to teach this stuff, EJB 3.1 is something I’d be happy to teach instead of the dread that would creep over me when starting an EJB 2 class knowing full well what was in store for my poor students. This framework truly simplifies Java Enterprise development by taking a huge bite out of the complexity of both developing and deploying.
Here are the final results of the Public Review Ballot for JSR #318:
SE/EE
|
The Executive Committee for SE/EE has approved this ballot. The Apache Foundation left following note regarding their no vote:
Apache Software Foundation voted No with the following comment:
The Apache Software Foundation must regretfully vote “no” for this ballot as the ASF contends that the spec lead - Sun Microsystems - is in violation of the JSPA, and the ASF does not support JCP participation by any entity that doesn’t comply with the rules and procedures agreed to by the rest of the JCP community.This is not a judgment about the technical or other related merits of the work this community is doing on the JSR.
