Help

Controls

PermLinkWikiLink

Built with Seam

You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.

The purpose of the JSR-299 specification is to unify the JSF managed bean component model with the EJB component model, resulting in a significantly simplified programming model for web-based applications.

Here we are developing the Web Beans RI (Reference Implementation) and TCK (Technology Compatibility Kit). Both are licensed under the Apache License 2.0.

[ SVN repository: committer, anonymous | RI JIRA | TCK JIRA | Development of Web Beans (RI and TCK, moderated) | SVN Commit Notifications | JIRA Issues Notifications ]

Recently Resolved TCK Issues
No issues found.

How does Seam relate to Web Beans?

The two technologies share a common goal of providing a unified, contextual, programming model for Java Web Applications. Both also enable EJB 3.0 components to be used as JSF managed beans, unifying the two component models.

However, Seam is a superset of WebBeans. You can really think of WebBeans as the core of a future Seam - it's how you will be able to write your components. From here, Seam goes on to fix many shortcomings in JSF and add page-oriented feature sets. Seam adopts and promotes a number of technologies (like Facelets as the preferred JSF view handler and then continues to leverage it to provide XHTML-based templating for PDF generation and e-mail composition). It also extends well beyond Web Beans, reaching into the security realm to bring viable security options to a Java EE application, with a specific solution for securing JSF views. The list goes on. Thus, Seam is really the bigger picture.

On the other hand, many features and ideas in Web Beans were inspired and tested in Seam first (as well as other frameworks, such as Google Guice).

Will Seam become Web Beans?

Not quite - Web Beans is the core programming model, so a future Seam version will offer both a Web Beans based core, with the ability to run Seam 2.x apps on it. Seam will continue to be the vehicle which delivers security, PDF rendering, email, BPM integration etc.

I want to help with Web Beans development and contribute code

Web Beans is a new project, so for now your best starting is to check out the current trunk from SVN. It's also worth reading our guidelines for Seam development as some aspects (e.g. coding style) apply.

Finally, pick an open issue and submit your patch. We typically grant commit access to Web Beans after a developer submits useful patches. Red Hat Inc. also hires exceptional contributors as full-time open source developers.

This is a list of the issues the Web Beans development team have marked as your best starting point:

Post Comment