Home/ Questions/Q 432277
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T20:03:30+00:00

I work on the JBJF Project on SourceForge and we want to improve on

  • 0

I work on the JBJF Project on SourceForge and we want to improve on the Database Access for this framework. Currently, it’s semi-flexible, but the access is done at the Task level.

We’d like to setup a simple Interface of some kind that’s generic in nature and can host the database access to/from JBJF. Thus, Framework classes don’t care what kind of database, they just call a method like getConnection() and a java.sql.Connection object comes back.

I’m wondering what would be better suited, a typical DAO layer with a single Interface or a Plugin type structure where we configure the Database Service in an XML file and the Framework loads the Plugin(s) when it starts up.

tia,

adym

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I was starting to think that Hibernate had gotten too big and bloated, but I’ve recently worked on a project using the latest 3.5 release and using JPA and they’ve definitely slimmed it down and made it much better than some of the other 3.x releases. I’d recommend JPA using Hibernate 🙂

    One of the great things about this approach is how good Hibernate is at dealing with multiple different database dialects. Our app runs on MySQL, H2, and SQLServer with no modifications (and probably would just run on the other major databases as well).

    • 0