aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes EJB perception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJB perception" Watch "EJB perception" New topic
Author

EJB perception

Juan Rolando Prieur-Reza
Ranch Hand

Joined: Jun 20, 2003
Posts: 236
I have a question about your EJB 3.0 book. What is the best way to convince management and customers to give the EJB architecture another try? They have a poor impression of the EJB concept from EJB 1, which EJB 2/2.1 was supposed to correct. So why should they try EJB 3.0? Is it better than old-fashioned using JDBC directly? Is it better than switching to Hibernate or Top-Link? Why?

Thanks for your answers.
PS. I myself have appreciated the gradual improvements to EJB and I myself amy not afraid of the "complexity" and learning curve, but others are afraid.


Juan Rolando Prieur-Reza, M.S., LSSBB, SCEA, SCBCD, SCWCD, SCJP/1.6, IBM OOAD, SCSA
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10046
    
163

EJB2.x was a bit cumbersome *compared to* EJB3. Looking at EJB3 specs and some sample examples(i havent yet started off on EJB3 yet), i certainly feel its far more simplified compared to earlier versions.

As far as comparing EJB3 with Hibernate and other ORM tools is concerned, i do believe that EJBs are not just an ORM tool, they have much more to it.
[ October 24, 2006: Message edited by: Jaikiran Pai ]

[My Blog] [JavaRanch Journal]
Raghu Kodali
author
Greenhorn

Joined: Oct 05, 2006
Posts: 18
To start with, EJB 3 specification has been developed by taking some of the proven best practices that have been in place for a while and been used by frameworks like TopLink etc..

Java Persistence API (JPA) is part of EJB 3 specification to address Object relational mapping problem. Both TopLink and Hibernate provide implementations for JPA specification, so it is not one over the other, they support the specification and in some cases add some value-add as they have been in place for a long time.

If you are starting with EJB 3, you need to learn some new API or annotations, but if your team is already familiar with POJO model and one of the ORM frameworks (TopLink, Hibernate,....) then you pretty understand the model that is used to develop object models.
The big benefit is that you are leveraging existing understanding but at the same time taking the benefit of standard, developers can learn one API/annotation to build ORM part of the application.
Ofcourse the simplicity of the specification also helps to leverage existing Java skill sets and come up to speed to EJB 3 in short time.

-raghu
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: EJB perception