Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Looking for solution for DB persistence

 
Tim Resh
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am looking for a db persistence package that is easy to use for POJO's. Package should use the POJO to keep the table structurally in sync. XML mapping or field named mapping. Validation call back if possible. CRUD and simple calls. object.save object.delete. AutoKey generation. 1to1, 1tom, mtom. some type of property file for sql queries and reports.

Hibernate is not an option at this time. Looking for simple to allow quick installation to current system of pojo's

Any help or experienced with existing packages is appreciated.
Thanks
 
Carlos Conti
Ranch Hand
Posts: 131
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tim,

I found myself in a very similar situation some months ago.

Persistence is not difficult to manage, however when problems arise most of the error information retrieved is not very accurate and doesn't help much. In my case most of the times trial and error and clues from forums like this helped me out. Now I am pretty confident with simple schemas as the one you propose, and in my case I worked with EclipseLink. The web is plenty of related information and with some research you should get it working pretty easily. You may define xml mappings or as annotations in the class files.

I am also pretty newbie with it, but as far as I know, there are other libraries such as Toplink which can even create the data schema for you. Which in my case is very useful to deal with several projects at a time.

But from my experience so far, I have successfully implemented CRUD applications with EclipseLink. I also like how EclipseLink manages history records. Really straightforward to create and maintain. However I believe this feature is a must in Persistence so all libraries may include one or other approach.

The way is difficult at first specially regarding synchrnizing object models (db data and running data) but after a while you can only take advantage of it.

Regards and good luck,

Carlos.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic