The Web Beans (JSR-299) specification is now available for public review.
Web Beans defines a set of services for the Java EE environment that makes applications much easier to develop. Web Beans layers an enhanced lifecycle and interaction model over existing Java component types including JavaBeans and Enterprise Java Beans. As a complement to the traditional Java EE programming model, the Web Beans services provide:
- an improved lifecycle for stateful components, bound to well-defined contexts,
- a typesafe approach to dependency injection,
- interaction via an event notification facility, and
- a better approach to binding interceptors to components, along with a new kind of interceptor, called a decorator, that is more appropriate for use in solving business problems.
Web Beans is especially useful in the context of web applications, but is applicable to many different kinds of applications and may even be used in the Java SE context, in conjunction with an embeddable EJB Lite container, as defined in the EJB 3.1 specification.
The Web Beans public draft is available in PDF or HTML format at:
- http://docs.jboss.org/webbeans/spec/PDR/pdf/Web%20Beans%2020081029.pdf
- http://docs.jboss.org/webbeans/spec/PDR/html/
or from:
Please send feedback on the public draft to:
- jsr-299-comments@jcp.org
An even easier way to learn about Web Beans is the Introduction to Web Beans guide available in PDF or HTML format here:
- http://docs.jboss.org/webbeans/reference/1.0/en-US/pdf/guide.pdf
- http://docs.jboss.org/webbeans/reference/1.0/en-US/html/
The Web Beans Reference Implementation and Compatibility Test Suite are being developed at:
This is a great time to get involved!
Wonderful news Gavin, downloading now !
Keep the good work Web Beans Team.
/peace
Congrats from the folks at Cirrus Gavin! I've really enjoyed using Seam and look forward to this worth addition to JEE.
Haha, great, awesome! :-)
Hi Gavin, I am studing the JSR 299. In Early Draft review, the specification mentions , and in Public Draft review, the specification mentions . what is the difference?
Congrats, Web Bean is fantastic.
No substantive technical difference, it's just that in the public draft we were more careful to characterize Web Beans as a service, with a (by analogy to the JTA transaction manager, or the Java security manager) instead of a component model with a container.
Please let us know of any feedback you have :-)
Hi Gavin,
I personnaly like Seam and how it seems to easy web apps developement, but i can't keep myself of thinking that all these new concepts such as web beans nmakes things look complicated. Why don't we just keep on working with simple objects as OO prescribes it, then use annotations to add specific behaviours to them.
What i liked a lot in Seam is the stateful side of it (with the new conversational scope) and that it solves the problem of the lazy initialisation exception on the presentation tier ..
QUESTION 1 / What does this specification really brings me as a developer ?
To me the next step after Seam is really what Spring is doing with Domain Driven Design and web apps developement which is represented by the ROO framework ..
QUESTION 2 / What is your answer to ROO ?