Are EJB still alive ?

Question

Do you still use session or entity EJB in your project ? Why ?

Answer 1

Ooo yes it is, my colleagues, got new project for mobile massages and the technology that they should use for that project are EJB 3.0 on a JBoss server... I'm wasn't have a role on that project, but I'm pretty sure that software architect wasn't drunk when he was design a system ;)

Answer 2

Yes, but EJB were stupidly complex for most use cases. Very clever, but real overkill in most cases. Hence the lightweight approach taken now-a-days.

Justin

Answer 3

AFAIU, it's used only for the legacy code written before lightweight frameworks (Spring etc.) hit the mainstream.

I suppose you should be very careful when deciding to use EJB in a new project.

Answer 4

We're working with EJB here and it works quite well with JBoss Seam and JSF, Faclets and MyFaces Trinidad. Good UI, Templating, AJAX and stable production 24/7 running on JBoss 4.2.

It's a good stack for business processes, workflows, messageing, webservices and ui control. Fast delivery of features, easy programming and stable ground based on entitybeans with mysql persistance.

I don't want to miss the featureset of EJB 3 for the tasks our product demands.

Answer 5

EJB3 is a vast improvement over previous versions. It's still technically the standard server-side implementation toolset for JavaEE and since it now has none of the previous baggage (thanks to annotations and Java Persistence), is quite usable and being deployed as we speak. As one commenter noted, JBoss SEAM is based upon it.

EJB 3 is a viable alternative to Spring, and the two technologies may become more tightly related. this article details that Spring 3.0 will be compatible with EJB Lite (which I'm not sure what that is, exactly) and possibly be part of Java EE 6.

EJB is not going anywhere.