In Relation To

Hibernate Validator version 4.0.0 Alpha3 is of now available. This implementation is based on JSR 303 Specification 1.0.CR1[1]. The distribution packages contain everything you need to get started.

Adding to the stockpile of features that I've packed into seam-gen in recent months, I just committed a new seam-gen command that generates a front-end to Seam's identity management API (JBSEAM-3717). Identity management is one of the most significant additions to Seam in the Seam 2 code base. But since its just set of framework classes, you need something to tie it into your application to truly appreciate (or even give notice to) its potential.

After an alpha, a beta, 2 CR's and countless nightly builds I'm proud to present the JBoss Tools 3 release!

One of the most wanted feature requests for our tooling is Maven integration/support for our projects, such as Seam.

I finally got around to weaving my modifications for adding GlassFish support to seam-gen (documented here and here) into the Seam project (JBSEAM-1619). While working on integration the changes, I managed to close the few remaining gaps and also add support for JBoss AS 5!

I'm pleased to announce the release of Web Beans 1.0.0.BETA1. This release implements around 90% of the JSR-299, Java Contexts and Dependency Injection specification. The only major feature missing from this release is support for annotating your beans using XML.

JBoss Tattletale 1.0.Beta2 was released today featuring new reports and important bug-fixes.

Following the Roadmap version 4.0.0 Alpha2 of Hibernate Validator is now available. This implementation is based on JSR 303 Specification 1.0.Beta4[1]. The distribution contains everything you need to get started. If not let us know what you are missing.

Remember the blog, How to create a visual DocBook editor in 10 minutes and how it described how to create a Docbook editor with the Visual page editor in JBoss Tools ?

I've had this idea for a while now about using XSDs in Facelets templates. I believe we should stop pretending that Facelets templates are XHTML documents and start treating them as unrestricted XML. This would give us the freedom to extend the XML dialect with XML Schema and take full advantage of the type enforcement, syntax recognition, and tooling support that XML Schema provides.