This article, the first in a three-part series, lays the framework for the rest of the series. It covers setting up a new project using JBoss Portlet Container and JBoss Portlet Bridge, configuring a JSF application to use JBoss Portlet Bridge, and the capabilities that JBoss Portlet Bridge provides to a JSF application.
In a new article Ryan Dewsbury takes a look at how GWT assists developers in terms of Ajax performance by providing image bundling, caching, and application compression. It also includes an excerpt from Dewsbury's book, Google Web Toolkit Applications.
This article discusses the integration of the grails-acegi plugin with a sample Grails application. As part of this integration, there are three major components which will be used – Groovy, Grails and Acegi Security.
Microsoft released a preview of Volta last month. InfoQ interviewed Didier Girard, CTO of SFEIR and GWT expert to ask how they compare and share his perspective on what they represent for developers. 1
JSF, DWR, and Dojo are all popular technologies in their own right. This article looks at how they can be integrated together in a portal environment. 12
Jboss Seam is a full-stack web app framework that unifies and integrates Ajax, JSF, EJB3, Portlets, and BPM. This excerpt from the to-be-released first book on Seam introduces Seam's capabilities. 17
The final article in the series, Ian Roughely completes the migration of a Struts app to Struts 2, by migrating the user interface - jsps & tags. 19
Struts committer Ian Roughely looks and compares a Struts and Struts 2 app, identifies how to convert actions and configuration from Struts to Struts 2, as well as identifying common components. 13
Struts committer Ian Roughely explains the architecture, request workflow, configuration semantics, and differences in the action framework in the new Struts 2 (formerly WebWork). 16
A detailed look at the implementation and architecture behind 2M line of code, truly mission critical Java application. 11
.NET and Java interop can be made really simple using a REST document centric approach. This article demonstrates REST for interop as well as POST-REST. 4