• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

"J2EE knowledge" means automatically "EJB knowledge" ?

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

I know that EJB is the toppest Java technology and I really try to understand it (based on my Hibernate experience, mainly)

I have a dispute with some of my "friends" regarding if "J2EE knowledge" means automatically "EJB knowledge", too. I know that EJB is part of J2EE but can you say that you are an experimented J2EE programmer (based on Servlets, JSP, JSF, JSTL, XML-XSLT, JAX-RPC knowledges) even if you know about EJB only that is a relational mapping tool (somehow similar to Hibernate) ?

Best regrads.
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I consider J2EE programmers to know EJB. Others opinion may vary.
 
Catalin Mihalache
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
sorry, but I didn't said "J2EE programmer", just "J2EE knowledge"!
 
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Catalinescu,

In my opinion, you can be a "experimented J2EE Programmer" (whatever experimented in details means ;-) even if you don't know EJB. Your application needs may fit exactly into the J2EE technologies without EJB's. I, for example, have a few servlet / JSP experience, no experience in Webservices and a lot of experience with EJB's.

However, EJB is not only a relational mapping tool. EJB is much more, and in our project we don't use this part of the EJB technology - we don't use Entity Beans. The main adventages of EJB's are (maybe this is an incomplete list - other opinions are welcome):

- Transactionservices
- Securityservices
- Single-threading model for the Bean Provider (=Programmer)
- Portability
- Messaging integration
- Timer services (singe EJB 2.1)
- relation mapping tool ;-)

Severin
 
Ranch Hand
Posts: 1312
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In my opinion,

If you have knowlegde in J2EE Techology , you should have standard knowlegde about concept of n-tier/multi-tier, concept of EJB ...
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic