hibernate vs ejb3 in seam

[600114046]

Hi,

I am looking to build a scalable high hit web app, which is db driven, using seam. So far the examples tend to be hibernate or ejb3 (entity beans)... I need to make a choice. I was wondering whether anyone could recommend why you'd use one approach over the other ?

Thanks.

[norman.richards]

I would recommend using the JPA APIs. (what you see in EJB3) You can still reach down and use hibernate-specific things if you need to.

[bytor99999]

So it is not really a question of EJB3/JPA or Hibernate, but which implementation of EJB3/JPA are you going to use. So in the examples, the ones that say are using EJB3/JPA, yes they are following the spec, but its implementation is Hibernate.

Hibernate implements EJB3/JPA plus it add much much more on top of it.

Mark

[svadu]

I would recommend using the JPA APIs. (what you see in EJB3) You can still reach down and use hibernate-specific things if you need to.

QFE. I prefer JPA over EJB3 but for simple reason that I run my software stack on Resin which isn't exactly EJB3 compatible atm.