Hi All

This is exactly not a question, but asking for feedback about an idea.
In a project at our organization, we are using hibernate with struts. We had a lot of forms which all require CRUD operations. Although hibernate does alot for us. Yet We developed a small and smart layer over hibernate. This layer automatically performs all CRUD (create, read, update, delete) operations. Now the time for getting data from the object and setting a hibernate object has also skipped.
The philosophy behind this is that GUIs are built over the relations of database. we call them mapping relations e.g.

1 GUI 1 Table
1 GUI N rows of 1 Table (like multiple entries)
1 GUI N Tables.
1 GUI

and definitly there are alot of other mapping relations of GUIs and Tables for which the layer can be enhanced.

The core functionality of the layer is that (for web) it just receives tyhe HTTP REQUEST object and does all operations itself. you just need to post your request to a central controller and it does EVERYTHING for ANY GUI. Developer just need to build a GUI.

I have planned the future enhancement of this layer, i.e. after creation of a database, every thing will be generated and ready to be persisted in database without writing a SINGLE LINE OF CODE.

Another approach on which this thing is being built is

1) FORGET ABOUT ATTRIBUTES, THESE ARE BUSINESS OF GUIs AND TABLES

2) WHILE DEFIING YOUR USECASES, JUST DEFINE THE PERSISTENCE SEQUENCE OF YOUR USECASE IN THIS UTILITY AT OBJECT LEVEL. SO WHEN YOU ARE DONE WRITING USE CASES, AT LEAST A DRAFT VERSION OF YOUR APPLICATION WILL BE RUNNING. ONLY BUSINESS LOGIC WILL BE LEFT TO FEED IN.


I just wanted to inquire that is something like it already exists in the market? AND DO YOU APPRECIATE PUTTING MORE EFFORTS ON THIS LITTLE TOOL?

PLEASE FULLY CRITICIZE TO IMPROVE AND APPRECIATE TO HELP ME KEEP THINKING ABOUT SUCH A THING.

Something similar is being built for JSF. See http://forum.hibernate.org/viewtopic.php?t=945552 and http://opensource2.atlassian.com/projec ... se/HBX-367 .

I'm in the midst of unit testing, so there will be something useable soon. The design takes individuals who are perhaps like yourself into consideration. For example, if you are interested in an hbm2Struts, you would make a StrutsExporter that would extend WebExporter.

This is code generation. If you are interested in producing web components that dynamically render as CRUD forms, you're alone ;-) Although this is certainly something that I am interested in much farther down the road.

If you are interested in sharing this, I'd recommend you tie it in w/ the various tools that are already available w/ the Hibernate Tools suite.

Sounds like the concepts are similar to that of Naked Objects. I recently found a J2EE project along similar lines called Trails although both of these take only a 1 GUI = 1 Domain Object view of the world, they could provide some inspiration.

Jon