• Post Reply Bookmark Topic Watch Topic
  • New Topic

PRO EJB 3.0: Reputation of EJB hurting the 3.0 specs

 
Branko Santo
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

Nice to see more people involved with tech books here with us ranchers

My questions is, how much is previous reputation going to hurt EJB as a whole, as we see all around EJB has been dumped for faster and better frameworks and even as the 3.0 version solves a lot of problems will people hesitate to embark on such a journey?

Sun has a problem that the pure size of Java these days is making it hard for them to implement new things quickly and that is why we see so many frameworks that solve some or all of the problems. And than Sun takes these ideas and puts them into the official specs. IMHO EJB is the way to go, but how many people share that opinion, are there any reserch results?
 
Sudd Ghosh
Ranch Hand
Posts: 191
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I too have a similar concern. After all the debacles with prior EJB 1.x, 2.0, etc - resulting in some massive project failures (I was part of some and have gone thru this ordeal), and the open source community taking advantage of that and coming up with superior solutions and consequently, the tech population starting to like the other frameworks like struts, JSF, spring, POJO, etc - I wonder what incentive a business group will have to venture out to EJB 3.0?? I am in a J2EE environment and I see it extremely difficult to convince the management that anything good will ever come out of the EJBs. I personally think that Sun was very slow in overhauling the EJBs.
 
Mike Keith
author
Ranch Hand
Posts: 304
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is true that EJB has had a mixed reputation. While session and message-driven components have been used frequently enough and had a relatively high approval level, entity beans have been cast as the anchor that has dragged EJB down. It is owing largely to this fact that EJB has achieved its tarnished image in the eyes of some.

We actually considered renaming the persistence part to something else outside of EJB to distance it from the entity bean. In the end, of course, we did give it a name, Java Persistence API, but still kept it within EJB 3.0. Having its own name will allow us to separate JPA from EJB down the road, though.

So while I can't say that everybody will look at the new spec and see it for what it is, a major shift in developer productivity, I do think that the message is getting out bit by bit. Hopefully everyone here will help carry that message, now, as well

-Mike
 
Branko Santo
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well I am always the kind of person to stick to the specs provided since they guarantee that it will work best with one another and surely will be checking out the 3.0 EJB thoroughly and hopefully it will catch on and make us all one big happy family

Thanks for the answer
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!