If you do the whole thing dynamically you lose all control, and you end up screwed when the framework guesses wrong and the user injects dangerous content into your system. If you do the whole thing with something like Stripes, your DB mapping object that you use for JPA is populated into your form elements automatically, and state is restored just by loading the DB object into the Action Bean and sending a forward to the form, which seems pretty easy to me. Validation is as easy as addition @Validate to the set method with what kind of validation you want, or writing a validation method that you annotate with @ValidationMethod. Persisting: objDao.save(obj); objDao.commit(); Dosen't seem very hard. If you value type safety (which I do) then Stripes/Spring DI as far as frameworks I have used seems as easy as it gets, certainly easier than Struts or Spring MVC, and I think less verbose than Wicket, though Wicket's templating system is pretty cool from what I've seen, though I would have to confess I've never actually done a large scale project in Wicket.
If I had one complaint about stripes it's that componentization seems difficult. Building a page with many user input widgets on it seems to be a bit tricky. With some inheritance and use of interceptors, you can achieve it to some degree, but it's not perfect. It's just a shame that the portlet spec is not better. Alex On Sun, Sep 27, 2009 at 6:40 PM, Steven Herod <[email protected]> wrote: > > On Sep 27, 3:54 am, Mwanji Ezana <[email protected]> wrote: >> On 26 sep, 04:20, Steven Herod <[email protected]> wrote: >> >> > I basically stopped paying attention to Java Web frameworks after >> > discovering Grails, although I'm still looking for something that >> > makes the whole forms based data collection side of things completely >> > painless. >> >> What do you mean, exactly? > > I mean, any application that involves a great deal of data collection, > (100's of fields over multiple pages) its just a PITA to do. > > Rendering read only vs edit views, restoring state, validations, > layout, form backing objects, transformation to a domain model, > persisting it etc etc. > > It's just time consuming, boring, and annoying, and whilst most > frameworks seem to have a portion of the solution, none make it > entirely straight forward. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
