The Google Web Toolkit (GWT) has attracted a lot of attention lately as a way to make it easier for developers to add AJAX Web 2.0 features to their applications. Like other approaches, the designers of GWT have tried to insulate developers from having to deal with the underlying JavaScript, which implements these features. GWT achieves this goal of simplifying the creation of advanced client-side JavaScript widgets by generating them from Java code.
JSF-Spring-JPA is the popular stack of choice these days, mostly to be used in my consulting and training purposes I’ve created a base project called MovieStore demonstrating the annotation-driven integration of JSF-Spring-JPA. JSF backing beans, spring service level beans and DAO’s are configured and integrated with annotations. Only the core infrastructure like datasource, entityManagerFactory or transactionManager are configured with xml.
The traditional way to integrate JSF and Spring was to define JSF beans in faces-config as managed beans and refer to the spring beans using the managed-property configuration. With the help of the spring’s delegatingvariableresolver the managed property is resolved from spring application context and JSF’s IOC injects the bean to the JSF Managed bean instance. I’ve written an article it about this way before.First approach is modelled as follows