Welcome to SolamenteNiel!

In the post #3 I described the steps for DWR-enabling the Spring services that I created in post #2.  This post will cover the implementation of the front-end.  Now the whole point of DWR is to enable server-side logic to be accessible via javascript, and that makes DWR very well suited for AJAX applications.

In the last post (part 2) I covered the creation of the service layer for my AJAX/DWR/Spring application called Bookmark Management.  In this post I will cover adding DWR support the service layer, so that in my next post I can build the AJAX front-end.

In the first post of this series I discussed the integration of AJAX-based applications with backend (server-side) logic in JAVA.  There are a variety of technologies to handle the complexity of AJAX/JAVA integration, and in my opinion Direct Web Remoting (DWR) is one of the best (if not the best) solutions.

In this post let me jump straight into a sample project that demonstrates the use of DWR with backend services developed with Spring.

As I mentioned in part 2 (Adding Appcelerator support to a web project), the weather data is coming directly from NOAA.  The NOAA SOAP Web Service is a free web service for accessing all the available weather data.  Unfortunately the web service is difficult to work with.  To me it looks like the web service was implemented based on the architecture of the weather data with minimal regard for the consumer of the service.  Subsequently I had to spend a lot of time figuring out how to parse the data with Groovy (more on that later).