Okay, this is my very first post here, though I have been lurking around much while learning the ins and outs of Spring+Hibernate.
A bit about what I'm trying to do with Spring+Hibernate right now: a Form builder which allows users to create custom web forms, something like this: http://www.form-maker.com/online_demo.html
Now, it's probably straightforward in the sense that I can dump all the key/value pairs into a database table. But what if I have certain fields that are to bind to certain domain objects? Say, the form contains the first name and last name fields that I must bind to a Members table. And the form can also contain user-defined fields such as hobbies, weight/height or whatnot that I would have no way of knowing beforehand.
My idea is that first name and last name fields are the mandatory fields that can map to the Members table, and I'd have another table to capture all the rest of the custom fields. Do you guys think this is logical? Or am I barking up the wrong tree? And is there a way to work this in using Spring and Hibernate?
So basically, once the user configures a form, it is persisted and possibly rendered to a JSP file or something. The form can then be called up by visitors to the website. The visitors can fill in the form and the normal validation and response will hold for this form.
I have been trying to get my head round all these, and am almost feeling that it might be too complicated or impossible to do. Also, I have been tinkering with all the different view technologies, like Tapestry, Spring Web, JSP/JSTL, and not too sure which one would best suit such needs.
Would appreciate if someone with a clearer mind to point me in the right direction.
Thanks and cheers!