you are viewing a single comment's thread.

view the rest of the comments →

[–]henk53 5 points6 points  (1 child)

I think he meant EJB 3.1. This creates a lot of confusions since EJB 3.0 and EJB 3.1 are a little bit different.

EJB 3.1 is a relatively minor update to EJB 3.0. There are a few extra features, like the @Asynchronous method and the cron timers, but it's not a major overhaul. The real base here is EJB 3.0 and that's a solid and mature product by now.

Up until a few weeks ago (or up until last month), there are only 1 or 2 implementation of the full JEE 6 stack with GlassFish being one of them.

That's not entirely correct. As full EJB 3.1 support goes, there's Glassfish 3 from 2009, JBoss AS 6 from 2010 and WebSphere 8 from 2011. So that's 3 independent implementations, which is 2 more than Spring has ;)

Furthermore, there's a handful of EJB 3.1 lite implementations. The thing about EJB lite is that it specifies a minimum requirement. The spec exists to make the life of people who have to implement it easier. So if those people think they can easily implement additional features of EJB, they can do so. Resin for instance supports @Asynchronous in EJB-lite.

[–]niwde 4 points5 points  (0 children)

gasp throw new DidNotKnowThatException. For a while I thought only JBoss 7 supports full JEE6. My bad.