In case you missed the news, JAX-RS 1.0 (JSR-311) was the first specification scheduled for inclusion in Java EE 6 to reach the final stage. My thanks to the spec leads, Marc Hadley and Paul Sandoz, the entire expert group and the very active community around JAX-RS for making this happen!
I've often wondered if it was possible to use Ajax to reload the main content of a web application without reloading the header, menu and footer. SiteMesh allows you to move these common elements to a decorator that gets wrapped around each page.
IWebMvc2 now includes the code to allow different (sub)sessions for each tab in your web application. The approach and the code is explained in detail.
Jonas Jacobi and John Fallows, the founders of Kaazing talk of the need for two way communication and compare it with established request-response and Ajax models of communication. They also touch on how WebSocket can be used in JavaEE applications and its impact on existing architecture and code.
Over the past two months or so we here at the web builer zone, thanks to Manning Publishing, have been publishing a comprehensive series on GWT. We recently published the last in the series and I thought that it would be a good idea to create a sort of index of all of these articles.
This article shows how it is easy to publish any graph of Java Objects to the web using simple annotations and without having to invent any new format. A simple example shows how one can publish a social network that links into the vast existing web of data. Jersey is the reference implementation of JAX-RS the Java API for RESTful Web Services.
Data Studio Developer and Data Studio pureQuery Runtime include a new feature called client optimization that enables developers to take advantage of the benefits of static SQL execution without having to modify their existing custom-developed, framework-based, or packaged JDBC applications. In this tutorial, learn how to use the tooling provided by Data Studio Developer to enable a JDBC application to use this new capability.
The model layer of a GWT application has to be a little bit smarter than the model in many traditional web applications. It needs to be responsible for notifying the view layer of changes, as well as for receiving updates to its own structure. In desktop Java development, this is accomplished through the use of PropertyChangeEvents and PropertyChangeListeners that bind the data from the model to the view components. The view layer "listens" for changes to the model and updates itself accordingly, using the Observer pattern. This can be done in GWT development as well.
Many principles that underlie the Java EE platform's design — especially, the use of synchronous APIs — don't apply to the requirements of Web 2.0 solutions. This article explains the disparity between the Java EE and Web 2.0 approaches, explores the benefits of asynchronous designs, and evaluates some solutions for developing asynchronous Web applications with the Java platform.
This is the third blog in the JSF 2.0 New Feature Preview Series. The previous entry covered packaging of resources. Now we'll cover the APIs that back this feature.
Google Web Toolkit (GWT) is an opensource project that gives you the tools needed to write Java using a Swing-like API. You then run/debug your Java code within your preferred IDE and immediately see the effect of what you wrote.
Here’s where Gnip comes in, an online message oriented middleware aka integration service provider, offering capabilities such as protocol abstraction, channel optimization through hub and spoke model, data standardization.
A detailed comparison between most popular java web frameworks. You will find it usefull if you are confused over 200 java web frameworks.
The GWT team has a very good tutorial for beginners. I've taken that tutorial and modified it to work with Instantiations GWT Designer. If you've wanted to get started with GWT painlessly then this tutorial is probably for you.