Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Industry use of EJB's

 
Justin Krettabull
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is the use of EJB technology in industry wide-spread and necessary? I'm considering studying for the SCBCD exam, but my company has a new policy forbidding the new development of EJB's...The architects and senior developers feel there is no need to use EJB's due to the added complexity and resource overhead. We have several applications that use EJB's written by 3rd party consultants. I'm wondering if its worth the time for me to go for the certification.

Justin
SCJP, SCWCD
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is the use of EJB technology in industry wide-spread and necessary?
wide-spread: yes
necessary: it depends there are other alternatives, too.

I'm considering studying for the SCBCD exam, but my company has a new policy forbidding the new development of EJB's...

What kind of company is that? Have you considered finding another job? Just kidding

The architects and senior developers feel there is no need to use EJB's due to the added complexity and resource overhead

What do they use instead?

I'm wondering if its worth the time for me to go for the certification.
It's apparently not worth to do it in the context of your current job, but it's definitely worth to do it for your own technological culture... Just in case you find yourself another job
 
Justin Krettabull
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's a quick explanation of why we don't use EJB's:

I'm a jr. java programmer at a fortune 500 utility company that has gotten burned several times in the past 4-5 years by 'top' consulting firms who write unreadable and unmaintainable(is that a word?) J2EE code. Alot of the problems we've had center around the consultant's use (or misuse) of EJB's (they're JSP's and servlets are bad too).

So, anyways, the in-house developers have to maintain this crap and our senior developers and architects have an unofficial rule to prohibit the new development of EJB's to reduce complexity in our new apps.

This sucks because I'm really anxious to learn EJB (wrote my first EJB the other night; AdviceBean).

Justin
SCJP, SCWCD
 
Valentin Crettaz
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm a jr. java programmer at a fortune 500 utility company that has gotten burned several times in the past 4-5 years by 'top' consulting firms who write unreadable and unmaintainable(is that a word?) J2EE code. Alot of the problems we've had center around the consultant's use (or misuse) of EJB's (they're JSP's and servlets are bad too).

I'm sorry but the fact that hot-shot-´┐Żber-consultants write crappy J2EE code doesn't make J2EE a crap in itself. I would be inclined to blame the management people in your company who hired those consultants in the first place and failed to assess the quality of what was delivered...

If I were you I would not worry too much about that and go ahead. You might not work for the same company your whole life... I know plenty of other companies who have had success with J2EE

Congratulations on your first bean
 
Trevor Luker
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
After using EJB's for a while I think the your company policy may well be right. The whole EJB container and the unnecessary complexity it entails needs to be completely rethought, particularly in the areas of CMT, CMP, CMR & deployment. I'm hopeful that EJB 3.0 through its use of the best parts of the Hibernate etc spec will go a long way to making this happen.

It is possible to build elegant, easy to maintain systems using EJBs however my experience is that not many people know how to (despite what they say). It's simply far too easy to get it wrong and end up with a monster.

For the majority of my systems I prefer to use Apache, Tomcat, JSP/Servlets and Hibernate/DAO - the systems work well, don't lack functionality and are much less complicated to build, deploy & maintain.

Your mileage may vary.

Treval
 
Lochana Lilly
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
is hibernate a replacement for EJB ?
 
Trevor Luker
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, it's not a replacement for EJB. It is an alternative for parts of EJB, in particular it's an alternative for Entity Beans and associated EJB container functionality. However, if you are studying for SCBCD I suggest you concentrate on the core exam requirements which do _not_ include hibernate. Until you pass that is...

Surf to http://www.hibernate.org/ if you want to learn more. The documentation for hibernate is superb.

Treval
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic