Richard answered O-R system
The main thing with JDO is make sure you're happy with the implementation and that it integrates well with your appserver, transaction management, etc. The second thing is its overall market support. I work for a company that has a vested interest in seeing it die, so I'll reserve comment on it other than to say: Just make sure you'll get the support you need on JDO. If you have a support contract with JBoss, we'll support Hibernate and CMP. If you use JDO, you'll need JDO support from a JDO vendor.
-Andy
A. Kevin Baynes wrote:
That's an excellent tip. I just got another email recommending JDO and re-affirming that CMP and BMP seem to be outgoing technologies.
I have some small experience with JDO, and none with Hibernate. I'll take a look at both.
What is an 'O-R system' ?
~akb
On Mon, 10 Jan 2005 08:02:34 -0800, Andrew C. Oliver <[EMAIL PROTECTED]> wrote:
All three major vendors include statements that can be summarized as "never use BMP" on their websites. BMP, in general, forces a N+1 load semantic.
Hibernate also has a programming model that makes it easier to seperate the two. For instance, objects retrieved are POJOs.
Consider Hibernate. It runs on all three and in plain java and is most similar to the future of EJB. The competitor of note is Toplink.
Both JBoss and Oracle support their respective O-R systems on other appservers.
-andy
A. Kevin Baynes wrote:
I think that my application is relatively simple, and I'm hoping to make the application as portable as possible. I'm trying to completely separate the business rules from the persistence mechanism, allowing customers to connect to their DB of choice. I'm looking for transaction support and single-signon.
It sounds like CMP may pose portability issues, and that maybe I should avoid it in favor of BMP?
What other features are most prone to affect portability?
Thanks.
~akb
On Sun, 09 Jan 2005 15:31:29 -0500, Cory Foy <[EMAIL PROTECTED]> wrote:
A. Kevin Baynes wrote:
Thanks, Andy!
If I understand you correctly, then the simplest thing for me to do is to pick an app server and write to it specifically, only taking on the task of porting to another app server as a last resort, right? If that is the case then it will probably be JBoss.
Actually, the way I read it was that to determine if your app is going to be portable across app servers, you have to see what features of the app servers you are going to use. In Andy's case, if you are using CMP, then you need to think about how you are going to make that portable. However, if all of your app uses features that are implemented similarly on the app servers, and you target the J2EE standard, then you should only have minor issues with portability.
Cory
_______________________________________________ Juglist mailing list [email protected] http://trijug.org/mailman/listinfo/juglist_trijug.org
