Help
Location: Charlotte, NC
Occupation: Principal Software Engineer at Red Hat
Archive

Seam Faces - Version 3.0.0.Beta1 is released. Several bugfixes as well as several new features have been included. This new version requires Weld Version 1.0.1.Beta1 or later. (Meaning GlassFish 3.1 or JBoss AS 6 M5+)

We have also begun integrating Seam Managed Transactions, however, this requires an optional dependency on the Seam Persistence Module.

http://seamframework.org/Seam3/FacesModule

<dependency>
    <groupId>org.jboss.seam.faces</groupId>
    <artifactId>seam-faces</artifactId>
    <version>3.0.0.Beta1</version>
</dependency>

Also note that JBoss Logging is now required instead of SLF4J.

<dependency>
    <groupId>org.jboss.logging</groupId>
    <artifactId>jboss-logging</artifactId>
    <version>1.0.0.Beta4</version>
</dependency>

Bug

  • [SEAMFACES-42] - IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method

Feature Request

  • [SEAMFACES-21] - raise before navigate event
  • [SEAMFACES-22] - create an input field container component that supplements a composite component
  • [SEAMFACES-54] - Need a producer for the standard Faces javax.faces.context.Flash object
  • [SEAMFACES-56] - Update Seam Faces to use JBoss Logging

Patch

  • [SEAMFACES-53] - The FlashScopedContext unnecessarily adds a fid parameter into the query string when only a single Flashcontext is active.

If you've ever programmed in PHP, Ruby, Perl, Groovy, and probably others, then you know how nice it is to have a central, official space for reference documentation and inline community feedback.

This is something that has sorely been missing from the JEE community, and something that has caused many disparate websites to attempt putting forward a weak effort in providing useful documentation -- you leave the community part aside to think that this is a good thing for any open-source technology.

A successful open-source community documentation initiative has:

  • Comprehensive documentation provided on a central, official website (http://seamframework.org)
  • Inline comments and user feedback.
  • The most common paths on the website are the most visible, intuitive paths.
  • Fluent navigation and document hierarchies. (The URL matches the Breadcrumbs matches the content. If users get lost, users give up.)
  • Accurate and relevant official information, well vetted information.

I'm sure there is more, but that's what I have at the top of my head.

Making progress happen:

In kick-starting my (hopefully long) tenure with Red Hat, I'm focusing on improving community documentation for the Seam Framework, and for Java EE as a whole. I've started by updated the Seam Framework website to more clearly display the links to Seam and Weld JIRAs; you previously had to do a little digging.

All of my efforts can be tracked here: https://jira.jboss.org/jira/browse/JBSEAM-4585

Please, I ask if you find any outstanding problems, or points of pain with the Seam or Weld documentation, to add it to this Jira. If you can't, then comment here and I'll see that it's addressed.

SeamFramework.org needs work, and I do think that the community really belongs on jboss.org, in order to fully get credit for their hard work and great achievements. Jboss.org also provides much of the functionality that I'm looking for in a community management tool, but we'll see what everyone wants ;)

Happy communities make happy software!