Tags
Authors
The RESTEasy project is an implementation of JAX-RS. I've just committed the docs for the first step of the integration into Seam. You need a nightly build of Seam 2.1 trunk (wait until tomorrow for updated docs in the nightly build) or better a current SVN trunk checkout.
On Monday afternoon I will be talking about Seam and Web Beans at the UK JBoss User Group in London.
Over on Thinking in Seam, I've been running a series on working with Google Maps using Seam and I thought it would be an idea to put the links to the series in order on here.
There has been a post or two regarding Seam and RESTeasy in the Seam forums, and the RESTeasy mailing list so I thought I would share my opinion as to where these technologies could fit together. I have been thinking about this since talking with Bill Burke at his JUG talk on RESTeasy.
We've released Seam 2.0.3.CR1. This is a relatively small release focussed on fixing up a few small issues with Seam 2.0, making our stable Seam 2.0 branch even better. The most significant change is an upgrade of Facelets for better JBoss 5 compatibility, but there are a handful of other changes that existing Seam users should look over. Please give the release a spin and give us feedback if you run into any issues.
The latest release of Seam 2.0.2.SP1 includes a completely updated reference guide chapter for deploying Seam on BEA's Weblogic . The primary focus was on working around several issues with Weblogic and EJB3 support.
The 2.0.2.SP1 release addresses two issues that were found in the 2.0.2.GA release.
I'm pleased to say we have released Seam 2.0.2.GA.
Seam 2.0.2.CR2 is now out. This release fixes almost all the known issues with CR1 release, with most of the changes related to minor problems with the examples and the documentation. The laundry list for the GA release is quite small, so I expect we'll have it out shortly. However, the exact timing depends on what kind of feedback we get from the Seam community. If you want to help us get it out faster, give 2.0.2.CR2 a test run and report back if you encounter anything out of the ordinary.