문제

My choice is between

  • Tapestry 5
  • Vaadin
  • JSF2

--- start EDIT 2010-05-13 18:04 --

  • Spring MVC (don't know why I forgot to mention this)

--- 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.

다른 팁

JPA2 being part of J2EE 6 fits naturally with its other components: EJB 3.1, JSF 2, CDI (Web Beans), etc.

If you consider other frameworks then you need to understand what features and benefits you gain by replacing J2EE 6 components.

Take a look at this blog post which describes how to apply JPA based persistence for Vaadin applications. It uses JPA2 provided by EclipseLink.

Try OpenXava, because in OpenXava JPA2 entities are the core of your application. Writing only JPA entities you get a full functional AJAX application.

I use Vaadin with their Spring integration coupled with EclipseLink and it works pretty well.

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top