• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Database access

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We start with existing database. We need Java objects. We need web access.

Very common problem, no? Every company has existing databases.

We know we no like ORM tools, we no like runtime fees.


What is best simple approach?


tx
J.

Not posted in ORM forum because we no like ORM suggests.
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


We know we no like ORM tools, we no like runtime fees.


The Open Source ORM's don't have any licence fees to pay.
 
Ranch Hand
Posts: 214
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is the reason you don't like ORM tools because they have a runtime license fee? Check out well-documented open source tools like Hibernate and/or Spring. There are others as well. None of these have licensing fees.

Otherwise you can communicate with your database through JDBC and try to roll your own persistence layer. However this route becomes needlessly complex in a big hurry. In fact, it is really a separate project all on its own.

If you do go this way make sure your design stays flexible.
 
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Have you looked at Data Access Objects?

Generating DAOs directly from your database schema provides a quick solution that is also a sustainable long term Java architecture that can evolve as Java persistence technologies change. You can find an example of how to do this here: http://www.codefutures.com/products/firestorm/

You seem to dislike the concept of ORM. Don't get too caught up on the specific technologies involved. That changes all the time and what's popular now may seem a poor choice later. Concentrate on the architecture.

You can find some advice about this issue here:
http://www.codefutures.com/weblog/andygrove/archives/2005/05/java_persistenc.html

Hope this helps
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic