The Artima Developer Community
Sponsored Link

Design Forum
Java Persistence from a (RDBMS) legacy perspective

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Tiago Antao

Posts: 26
Nickname: tiago
Registered: Feb, 2003

Java Persistence from a (RDBMS) legacy perspective Posted: Jun 27, 2003 2:57 AM
Reply to this message Reply
Advertisement
Hi!

Looking at most discussions about enterprise persistence with Java (read CMP, BMP, JDO, Session + JDBC, JDBC, OR tools, ...) they seem to be from a perspective of a completely new application (with a new datastore)..

My question would be: if you have an old RDBMS fully functioning, you want to maintain the schema, but just upgrade the application arround it from X(X: put your prefered legacy here) to J2EE, what thingy would you prefer?

As I see it trying to retrovert anything via other than JDBC can be, in a medium/complex schema, very painful. Where are the flaws of my reasoning?

Topic: Containment vs Inheritance Previous Topic   Next Topic Topic: ArcStyler and MDA projects

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use