Win a copy of Java Concurrency Live Lessons this week in the Threads forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Why EJB3?  RSS feed

 
Bart Allen
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With EJB 2.x there were a few situations where you would use EJB, and some where you clearly would not.
You would use for MDB/JMS, distributed components, remote access over RMI/IIOP, multiple client types-- and possibly CMT, simplication of multi-threaded code, and declarative security.
Has this list become more expansive with EJB3?
What new situations does it make more sense to use EJB3 than POJOS or alternative technology?
 
Debu Panda
author
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think you have to read the chapter 1 of our book why you would EJB 3 http://www.manning.com/panda/panda_meapch1.pdf
 
Reza Rahman
author
Ranch Hand
Posts: 580
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bart:

A short answer to your question is that EJB 3 does not add very much new functionality other than making EJB far more usable and practical. AOP support through interceptors is really the most notable "addition". Annotation based DI is the other huge improvement over JNDI lookups.

What EJB 3 gives you is the abilty to harness the full power of enterprise services while writing nothing more than POJOs with annotations. I would ask you to take a look at a sample chapter from our book and see for yourself if EJB 3 is worth your while...

I would venture to say EJB 3 has become the simplest way of implementing common functionality such as declarative transcation management, state management and ORM-based persistence.

Reza
[ March 13, 2007: Message edited by: Reza Rahman ]
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!