In the first blog entry of this series, we showed how to configure a message body reader (MBR) on an instance of Client. This blog entry will focus specifically on the topic of configuration in the JAX-RS 2.0 Client API.
This is the second blog entry on series of blogs about JAX-RS 2.0 Early Draft. Today I'd like to discuss the Generic Interface for building and submitting requests in the Client API. See last week's blog for an introduction to the Client API.
The Early Draft for JAX-RS 2.0 (JSR 339) has been submitted for publication. I plan to use this blog to highlight the features in the new spec, and in this entry I'll start with the most requested feature: the Client API. This API can be broadly divided into 4 areas: the fluent API, the generic interface, configuration and asynchronous support. In this blog entry we'll explore the fluent API.
In my last blog entry, I described VideoSharing which is an application that uses Web sockets to remote UI events and enable participants to control HTML5 video players remotely. Today, I'd like to share with you a similar type of collaboration application, but this time one that uses other HTML5 features: namely, 2D canvases and client SQL databases. The name of this application is...
Some of you may have heard about the recent support for Web Sockets in Grizzly and Glassfish. In this blog, I will show you a simple Web application called <em>VideoSharing</em>. VideoSharing is web application in which you can control and HTML5 video object remotely using Web Sockets and Glassfish. The basic idea is to intercept video events like "play", "pause" and "seeked" and remote them using Web Sockets to control another player. Although there may be some use cases for an app like this (e.g., coaching), the real objective of this exercise is to the low-latency of the Web sockets implementation in Grizzly/Glassfish.
Web Services and XML
During the last few weeks, Marc H., Paul S. and myself have been exploring some ideas to support Hypermedia in Jersey. The outcome of this investigation is an experimental implementation that is available in Jersey's trunk (module version 1.2-SNAPSHOT). Exactly what it means to support hypermedia is still an area of research, and some other implementations of JAX-RS (notably RESTfulie) have also...
The Sun Mobility Platform Telematics demo, co-developed by Oracle and Sun, was showcased at Oracle Open World this week. It was shown as part of a presentation on Monday and at the Berkeley DB (BDB) booth for the rest of the week. The demo shows a simulation of vehicles synchronizing events collected on a local database (BDB) to a back-end Oracle database. Events collected from vehicle sensors are stored in an embedded BDB database and periodically synchronized; in addition, critical events are reported immediately using the capabilities of the Mobile platform. A JavaFX front-end was developed to increase the demo's coolness factor. There's a link to a short screencast in this blog.
As Ryan described in his recent blog, we now have support for Java SE clients in the Mobility Platform. Mahesh Sharma, a student and Sun ambassador in India, has been working on a port of this library to the Android platform. As part of his work, Mahesh also ported the UI of our MusicDb demo and has proven that Android is a great plaform to run SGMP applications.
The Mobility Platform team has been working on a number of new features and enhancements since the release of GlassFish Mobility Platform v1.1 in February 2009. One of those features is the ability to run the Mobility Platform software on top of Glassfish ESB. There is a clear synergy between the Mobility Platform and Glassfish ESB. The former is all about mobilizing the enterprise, while the latter is about integration of enterprise and legacy information systems. By running the Mobility Platform on top of Glassfish ESB, as opposed to just Glassfish, it is possible to write enterprise connectors that sit on the enterprise bus and can mobilize all sorts of information systems.