Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
My choice is between
— start EDIT 2010-05-13 18:04 —
— stop EDIT 2010-05-13 18:04 —
I like Vaadin most, because it seems to come with all the look-and-feel features out-of-the-box, I wonder if anyone has experience with Vaadin and JPA2, preferrably EclipseLink.
JPA2 is absolutely essential, the Web2.0 framework must integrate with it.
Thanks
Err
—
JSF 2.0 and Wicket 1.4 are first class candidates: they just work with JPA 2.0 and provides support for the Bean Validation API (JSR 303) which is in my opinion a very important part of the question. Have a look at this blog post for more details on this.
To be fair, I’ll mention that Tapestry 5.2 (not sure it has been released) will also provide integration with JSR 303 as detailed here but I’m not in love with Tapestry.
Regarding Vaadin, it seems that things are more complicated than with “regular” web framework and JPA 2.0 support to JPAContainer has yet to be added (Ticket #4298).
I’d go for JSF 2.0 or Wicket.