In Relation To

So you need to deploy to WebSphere, and you really want to take advantage of all the benefits of Seam including EJB3 - but your not sure where to begin?

The seam community site went live exactly one month ago, and already boasts more than 1000 registered members, with twenty-something people signing up every day. The new forum is buzzing, and we're starting to get lots of useful information up on the wiki.

One of my first tasks since starting at JBoss/Red Hat was to investigate and document container interoperability. What I found is what I expected - various tweaks, settings and library requirements depending on what container is being deployed to. These have more to do with specific server needs rather than anything Seam is requiring (mostly).

The last year we have been working full time on JBoss Tools and JBoss Developer Studio. One of the challenges we had were to add support for JBoss Seam in Eclipse. Similar to what the Seam team did for the underlying frameworks (JSF, EJB3, JPA, etc.) we had to do integrate/adjust for the various plugins that exists in the Eclipse family (WTP, JSF, Dali, etc.).

Recently the EE6 co-lead, Roberto Chinnici, blogged about the state of profiles in EE6, and requested feedback on which direction the group should take. This was also posted to InfoQ and TSS. Essentially we have a choice between two options:

I'll highlight a few of my favourite features of Seam 2, then go on to discuss how where Seam will go over next year, and finally introduce Web Beans.

It's been quite some time since the latest release of Hibernate Search, but since the code base has been fairly stable and bug free, we have been holding it until now. But there are some interesting features that could not wait anymore:

Well, I'm safely home after my first JBossWorld, and I wanted to share some of the highlights for Seam at JBossWorld Orlando - lots of presentations about Seam, and more on RichFaces, Hibernate, Tools etc.

The Seam community finally has a new home. Yes, everyone's been begging for this for, like, forever, but we wanted the Seam website to run entirely on Seam, which meant we had to build the infrastructure first.