J2EE programmer for JTG..
Originally posted by Marcus Hathaway:
Hi guys,
Thanks for the replies.
Mark....what are your reasons for suggesting EJB3 over Hibernate? I don't have any real production experience with either and have simply being learning Hibernate over the last few months...my understanding is that EJB3 and Hibernate are two of the same kind of thing (in terms of being persistence models). I'II be looking into EJB3 in more detail soon once i feel i've got a real understanding of Hibernate, its advantages and limitations.
So I guess what my question is...why would EJB3 suit this kind of architecture better than Hibernate? My motivation for the post is really to try and move away from the 2-tier architecture but unsure at present how to best achieve this (or if possible to achieve this) using Hibernate in a multi user Swing application.
![]()
Not knowing EJB3 in any detail, i just wondered why you'd favour this approach.Personally, I would take the Swing to EJB 3 on JBoss to Back End Database architecture.
"Currently each client app configures its own Session Factory locally, connecting to a remote database."
Which is two tier.
Originally posted by Marcus Hathaway:
Absolutely correct....this is the motivation for the post to try and get some ideas on how i can move away from this USING hibernate.
I'm definatly going to start exploring and having a play with EJB3, so thanks for your comments. However, has anybody any suggestions for trying to achieve a n-tier architecture with a rich client using Hibernate? Am i flogging a dead horse with this![]()
Do not threaten THIS beaver! Not even with this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|