aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes EJB in jeopardy ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJB in jeopardy ?" Watch "EJB in jeopardy ?" New topic
Author

EJB in jeopardy ?

Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

Hi.
I'm not going to ask you about the next steps in the next EJB specification since this article Mike Keith on EJB 3 do this.
But do you think that EJB is a specification in jeopardy ? (Richard Monson-Haefel said, the whole JEE platform in jeopardy) ?
In jeopardy here means, it will not be popular,it will be used widely amony the developers.
Yes sure, EJB still has its -strong cards- especially in message-oriented applications or distributed transactions.
But Hibernate and Spring really raised the bar so high and EJB may not be able to catch them.
Please don't get me wrong, I like EJB and I wrote some of them (since EJB2.0 specifications), but you as an author who wrote a book about EJB means you still believe in EJB.
So do you think EJB could come up for a breath of fresh air ?
Thanks.
Debu Panda
author
Ranch Hand

Joined: Jan 21, 2007
Posts: 100
I would say "EJB 3 is the savior!". Prior to release of EJB 3/Java EE 5, EJB 2 /J2EE were indeed in jeorpardy!. I criticized J2EE for its complexities in many of my blogs and articles. I strongly believe that EJB 3 has the power to save the diminishing Java platform.

See our chapter 1 how EJB 3 addresses the complexity in development http://www.manning.com/panda/panda_meapch1.pdf


Author: EJB 3 In Action (http://manning.com/panda)
Reza Rahman
author
Ranch Hand

Joined: Feb 01, 2005
Posts: 580
    
    5
John:

The question you ask clearly has no black and white answers. Truth be told, only you can be the ultimate judge of this question.

EJB 3 has all the goods to meet and exceed the demand of Java EE developemt simplicity and elegance. However, I don't think it's going to be easy to get over the EJB 2 quagmire. It really depends on whether people are compelled to take a good look at EJB 3 and not prejudge based on what was true in the past.

Reza
[ March 13, 2007: Message edited by: Reza Rahman ]

Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
Sudd Ghosh
Ranch Hand

Joined: Oct 23, 2002
Posts: 187
I was kind of getting impressed by the architectural changes in EJB3.0 compared to EJB2.0, after going through Mike Keith's JPA book, but then I came across the complexity in annotations - so many of them. I think if there was a way to simplify this, that would have been of great help. I understand it is a framework specs and it has to accomodate everyone's needs, has to accomodate all kinds of relationships, etc.

I definitely liked the conceptual changes in EJB3.0; in a way these changes aligned EJB3.0 with other event-driven framework's backend, like keeping one request in one JVM (no need of remoting), having only POJO entities (no entity beans), etc.. Hence the learning curve will not be that steep if one is familiar with any such framework's backend.


SCJP 1.4, SCWCD, SCBCD 1.3
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Even though EJB 3.0 has simplified things , organizations haven't forgotten the complexities of EJB 2.x and may be they are hesitant to move to new version.And also many have moved to Spring,Hibernate frameworks and may not have compelling reasons for switching.

Even though EJB 3.0 is standard many would argue that frameworks like Spring,Hibernate work on any application servers and possibly with little porting involved.


Groovy
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

I was kind of getting impressed by the architectural changes in EJB3.0 compared to EJB2.0, after going through Mike Keith's JPA book, but then I came across the complexity in annotations - so many of them. I


Is it just the number of annotations that cause concern ? If I am not wrong one can just use default values for many of them.
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

One more point - DI only works if the client is running in app server. If it is running outside , JNDI lookup code has to be written. Is there any way we can avoid this ?
Reza Rahman
author
Ranch Hand

Joined: Feb 01, 2005
Posts: 580
    
    5
Pradip:

You may avoid using lookup code in the client using an application client container (ACC). We talk about this in the book. Right now GlassFish has one, but JBoss does not have an equivalent.

Reza
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30764
    
156

Interesting topic. Hibernate et al address the entity bean part of EJBs. EJB 3 moves to the JPA spec (which Hibernate implements.) So it seems like they are getting the controversial part out of EJB leaving it to be session beans and MDBs.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8919

Originally posted by Reza Rahman:
Pradip:

You may avoid using lookup code in the client using an application client container (ACC). We talk about this in the book. Right now GlassFish has one, but JBoss does not have an equivalent.

Reza


Thanks but it doesn't look like it is a standard , so there is a concern.
Reza Rahman
author
Ranch Hand

Joined: Feb 01, 2005
Posts: 580
    
    5
Actually the spec addresses application clients. This has been the case in EJB 2 as well. Many people just don't know about it.
Debu Panda
author
Ranch Hand

Joined: Jan 21, 2007
Posts: 100
Yes, EJB 3 requires injection in the application client container. JBoss not being EJB 3/Java EE 5 compliant yet they do not support for injection in ACC or web container
Debu Panda
author
Ranch Hand

Joined: Jan 21, 2007
Posts: 100
Forgot to mention that the source code examples that we provide for both Glassfish and OracleAS uses injection in the application client container
Shyam kumar
Ranch Hand

Joined: May 21, 2006
Posts: 146
Hi Ranchers,

I'm new to EJB, and currently studying K&B HF EJB2.0 book. After going thru the discussions i want to know is it worth going thu EJB2.0 at all. Should'nt I jump to EJB3.0 straightaway?

Naveen
Christophe Verré
Sheriff

Joined: Nov 24, 2005
Posts: 14688
    
  16

After going thru the discussions i want to know is it worth going thu EJB2.0 at all. Should'nt I jump to EJB3.0 straightaway?

I feel that it is still useful to know about 2.0, as there are lots of jobs using it. 3.0 is still fresh. Whether or not to take the certification depends on people though. If you're working as a programmer, you may find it useful to know about it.


[My Blog]
All roads lead to JavaRanch
Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

If you are going to use EJB2 in your job, then study it.
But if you are not, I don't suggest you spent alot of time playing with it.
Shyam kumar
Ranch Hand

Joined: May 21, 2006
Posts: 146
I think going though EJB2.0 is worth an effort as there are jobs for it in the market. But I will keep an eye on EJB3 also.

Thanks a lot for the info
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: EJB in jeopardy ?