• Post Reply Bookmark Topic Watch Topic
  • New Topic

Comparison / Review question

 
Ram Gokul
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Authors ,

We have several light weight J2EE applications that we use for connecting with Oracle . In all of these cases , we are connecting to the DB using simple DAO access with no EJBs running . Going forward we want to take 2 approaches , either use Toplink / Hibernate / other ORM models or use EJB 3.0 to talk to DB . For projects that are in begining stage which of these 2 approaches do you advice ?. What are their pros' and con's from the perspective of manageability and scalability ? Till now we were more into web component part of it , now we are moving into Business component part of the system.

Thanks,
Ram
SCJP/SCWCD
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You should have a search of our ORM forum (where this question would be much better suited). The pros and cons of one ORM over another are discussed there often.
[ August 14, 2006: Message edited by: Paul Sturrock ]
 
Ram Gokul
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I did not ask for the comparison over 2 OR models . I asked between EJB 3.0 vs O/R products like Hibernate / toplink .which part of my posts made you think so ?

Anyhow the author has answered the same question by another user.
 
Mike Keith
author
Ranch Hand
Posts: 304
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ram,

Let me just say also, in addition to what I said in the other thread,
that it is even more important for you to use the standard API because in terms of managability and scalability there may be feature trade-offs between the different vendors that might be very important to you. The JPA standard will allow you to change vendors if the necessity arises. If you are talking to an Oracle database, for example, then Oracle TopLink will offer you more integration with the database than other implementations. However, this puts you back in the proprietary feature domain again, so you need to be careful what price you are willing to pay for the features that you want to use. Regardless of the implementation, you should start with JPA and then if you need proprietary features then you can use them in addition to the JPA APIs. Just remember to keep them isolated from the rest of your code so that if you want to change vendors again then you have all of the vendor-specific features in one place, not scattered across your app code.

Regards,
-Mike
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!