• Post Reply Bookmark Topic Watch Topic
  • New Topic

Why use EJB 3.0 and forget my Hibernate Based Framework?  RSS feed

 
Luiz Reginaldo Curado
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Today several applications were developed using Hibernate to replace the tasks performed by Entity Beans, in part due to the complexity of the development of BMP and also CMP.
We have developed several frameworks that today works using Hibernate, and this frameword can be easily learned by new developers.
So, why must I use EJB 3.0 and forget my Hibernate based Framework ?
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is no "must", but there might be a "should".
It's almost always preferable to use a standard way to do something over using some homegrown solution.
Not only will you (once it settles and people start using it elsewhere) be able to find people more easily who require less or no training, but as it's used by many and maintained by a major group there will be a better chance of (potential) problems being found and fixed than with your private solution.

Of course you should first weigh the cost of conversion against the potential benefits, but for new projects I'd definitely take the common standard as a strong candidate when investigating possible architectures.
 
Mark Spritzler
ranger
Sheriff
Posts: 17309
11
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
And also remember that there is a difference between a specification and an implementation of the specification. Hibernate 3.x is an implementation of the specification.

Mark
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!