I want to introduce POJO Jenerator, a code generator I've built over 10 years of Java web development. I have been using it exclusively for my own development, and it has saved me immeasurable amounts of time and frustration.
I've also found it to be a very useful teaching tool for bringing new developers up to speed in how to architect and construct a Java web-app.
In brief, you specify the name and attributes of an object, and POJO Jenerator will create for you:
- A DDL statement to create your database table
- A JavaBean class to represent rows in the table
- A full-CRUD, native JDBC persistence layer (DAO pattern class) with support for transactions
- A full-CRUD, working web-based AJAX GUI prototype
- I've recently added support for enumerations as well
Check it out here: What is POJO Jenerator?
(It's totally free.)
I'd be interested in feedback from those who actually try it out and play with the generated code.
I'm also interested in extending the tool to generate code for GWT, and possibly other platforms.
Please contact me: firstname.lastname@example.org if interested.
what? 4 servlets needed for the web.xml? really?
Not sure I understand what you mean. 4 servlets is too many?
No answer. Well, I guess I'll take a guess that you think 4 servlets to implement full CRUD capability is too many. The only thing I can think of is that you would prefer to combine all or most of that functionality into a single servlet, and then pass in parameters to specify whether the user is adding, updating, deleting, etc.? There are merits to that approach, but also pitfalls.
This is precisely the kind of discussion I wanted to foster, but of course it won't do much good if no one participates or follows through by explaining how it is you'd prefer to see it done.
However, this is all just academic. To see what it does, do me a favor, and go to this URL: http://www.timechannels.com/EmployeeDisplayRecords
This is an example of what POJO Jenerator produces. Go ahead, enter some new records, edit them, delete them, etc. Play with it a little. Then ask yourself this question: how long would it take you to build that functionality, for that example table, using your current tools, technologies, techniques?
If the answer is anything more than 10 minutes, you really owe it to yourself to check out POJO Jenerator. And if you have any ideas for extending POJO Jenerator to support alternative technologies, I'd have to think it would be a worthwhile endeavor for you to participate in that. (Imagine never having to write that kind of code ever again...)