Masoud has a nice Detailed Writeup explaining how to configure OpenMQ (the GlassFish JMS implementation) to run over HTTP. This is very useful in constrained situations, for example... An untrusted applet can communicate back to a server which it is initiated from (server which hosted the applet and delivered the .class and jar files). So your applet can either use mq protocol or it can use JMS over HTTP protocol which is shown in the sample.

BTW, Masoud also briely mentions the new UMS feature in OpenMQ and positions it relative to JMS over HTTP. Full details in Masoud's Writeup.

Sailfin CAFE is a new framework that simplifies the development of Converged Web apps. It can be used with Sailfin v2 and points to Sailfin v3. The project just launched and we want your feedback and participation. Check out Binod's Writeup, Sreeram's Mail Post and the slides from TS-4929 (id:contentbuilder / pw:doc789). Sailfin CAFE is a key step towards yet another "v3" container in the GlassFish family joining GlassFish v3 Server (out in September) and OpenESB v3 - making good progress through Project Fuji. The WebSpace Server is also going v3 but they have not yet started working on their builds.

OpenMQ 4.3 is now available (download). This release will be included in GlassFish v2.1 but also is useful on its own. One of the most interesting pieces is the new http-based Universal Messaging Service which can be used to access OpenMQ from a browser using AJAX, as well .Net, Python, Ruby, and many others (including Java!) - see Intro, Samples, Protocol and Configuration. Other functionality includes new platforms (AIX, Oracle 11g, Windows Vista, Windows Server 2008), a new installer, and additional Samples for things like talking to HermesJMS and STOMP.

Sun's distribution of OpenMQ still uses the "Sun Java System" brand but it follows the standard GlassFish Enterprise Business Model - see Product Page, Documentation and Downloads. And you can can purchase Commercial Subscription Support.

Ever been in a Web App that seems to be stuck in the (slow) "https:" protocol? Jan has your solution: downshift! Check out his explanation of How to write a WebApp that switches between HTTP and HTTPS. Jan's note explains how to use security constraints and Java ACC to solve the problem. The note also includes a sample (see WAR) and instructions on how to run it on GFv2 and GFv3 Prelude.

NB - when I read the title I immediately thought of this Downshifting (specially on older cars where the Syncromesh didn't work as well). I'll confess that I was not even aware of the more modern Downshift :-)

A compilation of today's news of interest:

Kshitiz has a note on the new Java-based Converged Load Balancer that will be part of SailFin and GlassFish v2.1. The CLB handles both HTTP and SIP traffic and can be used with and without a hardware IP sprayer. Check Kshitiz's Detailed Writeup for details on load balancing algorithms and configuration options.

Annotations are a first-class language feature in Java (tutorial, jsr-175). A standard specification like JAX-WS introduces standard annotations but custom annotations can be equally useful. Kohsuke uses a custom annotation to take advantage of a SPI (InstanceResolver) in the JAX-WS RI in GlassFish. The result is that adding a simple annotation (@HttpSessionScope, in the com.sun.xml.ws.developer.servlet package) on a class tells the JAX-WS RI to create one instance of the class per each HTTP session.

Like any other non-standard mechanism, adding the annotation creates a dependency on a specific platform, but the dependency is explicitly declared (usually via an import statement), and the result is really clean an compact. Check Kohsuke's blog for details.