• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Is J2EE Copying ideas?

 
guru prasanth
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
Is J2EE not copying ideas from other open source like Hibernate,Spring,Aspects,etc?I have been reading and working on hibernate,struts and spring framework recently.
Suddenly i find in newer version of j2ee they have copied the concepts from Spring.Please let me know if my understanding is correct or not

Dependency Injection: In earlier version of j2ee JNDI was being used.Suddenly in j2ee 1.6 or to be more precise in EJB 3.0 this feature is being introduced.
This is the same period in which Spring's popularity has also grown.

OR Mapping: Same as above.Earlier version of EJB had a complex way to define Entity relationships.Suddenly in EJB 3.0 they eased all the relationship.The
new version of Entity bean and JPA looks more or less like hibernate.

Can some one let me know that prior to the creation of J2EE 1.6 what made the people who designed J2EE 1.6 to arrive at these decisions.

Moderator though it's not a scea certification question i thought this is the best place to post this questions probably becuase there are many present and future architects.

 
Dmitri Ericsson
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Those ideas are already in Java EE 5. The ideas are not new, I think it is good that they created a standard way of doing things. Not better of worse, just standard. And the reason why ORM in Java EE 5 looks like hibernate is that Hibernate team was involved in development.
 
guru prasanth
Ranch Hand
Posts: 103
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dmitri,
Thanks for correcting me.It's not J2EE 1.6 but 1.5.In J2EE 1.5 is Dependency Injections used instead of JNDI Or like spring can you inject between the classes too?
There is lots of similarity between spring DI and J2EE DI.Like you can inject either at consturctor level or at method level.
thanks
guruprasanth
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's not copying. It's forming a standard specification for these technologies. For example, before the Java Persistence API came out - Hibernate, Toplink and various other ORM implementations provided ORM services in their own unique way. Switching between those implementation wasn't either possible or easy. However, the JPA spec introduces a standard for ORM implementations. So vendors like Hibernate, Toplink and other JPA compliant implementations are expected to provide their services as dictated by the spec. What this means is, if you code your application to follow the JPA spec, then your application is portable across Toplink, Hibernate etc...
 
prathap venkata naga yelugula
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ,
Just check with what are J2EE Specification concepts and What are Sub-Specification Concepts.

Don't consider flavors of Above Specifications.Those are one type of implementations.

For Example , Come to JPA , it has some implementations by other Organizations -- 1, Hibernate 2, IBatis. Like that.



Cheers!
Prathap.
 
sivan jai
Ranch Hand
Posts: 115
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gavin King the creator of Hibernate was in the EJB3 expert group and obviously it has all the features of Hibernate (in a good sense I mean) - that is the beauty of Java technology it is a community driven tech.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic