BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person or online.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or online.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Web Beans JSR 299 approved by JCP for further development

QCon New York (June 13-15): Learn best practices from senior developers at early adaptor companies.

Web Beans JSR 299 approved by JCP for further development

Bookmarks

Jun 07, 2006 1 min read

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
The new Web Beans JSR 299 has been approved by the JCP executive committee for further development.  Web Beans aims to enable EJB 3 session and entity beans to be used as JSF managed beans (known as actions in other frameworks) eliminating the dual layers of web actions and EJB's common in web apps. Instead, EJB's will BE the actions. Web Beans was first submitted to the JCP this past May by JBoss,  with support from Oracle, Sun, Borland, and Google. 

A number of people are calling Web Beans as a standardization of JBoss SEAM. Spec lead Gavin King insists that Seam standardizes some of the best features from a nubmer of frameworks, such as some of the first class constructs for modelling user interactions in use within frameworks like JBoss SEAM, Struts Shale, and Oracle ADF.

Some specifics from the proposal include:
  • Changes to EJB 3 that will be needed for EJB's to act as JSF managed beans.
  • Annotations for manipulating contextual variables in a stateful, contextual, component-based architecture.
  • An enhanced context model including conversational and business process contexts.
  • Extension points to allow the integration of business process management engines.
  • Integration of Java Persistence API extended persistence contexts.
EJB, which began as a framework for distributed transactional components. has typically been used by developers as a transactional services layer, completely divorsed from the web tier.  This JSR recognizes that the majority of developers using EJB are using it to build web applications and will attempt to standardize the binding between web and EJB's, which (among other things) will eliminate the 'glue' presentation logic typical in the presentation tier before calling the services layer. Oracle has been doing this for some time with ADF + JDeveloper, and as does the more recent JBoss SEAM.  

Support for this standard among the executive committee was strong and unanimous.  BEA commented that Web Beans "appears to be a sufficient challenge to achieve, but, in light of the overwhelming support at this stage of the process, we are prepared to see it go ahead."

JSR 299 will be the first JSR ever led by JBoss. The expert group for the JSR will be formed over the next few weeks.

Rate this Article

Adoption
Style

This content is in the Architecture topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • I like it

    by Tomasz Blachowicz,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Great news for the community I believe. Gavin King has a huge impact on JPA and EJB3 specification which are important innovations in Java EE. JCP299 seems to be very interesting and innovative initiative. In my humble opinion this one could be the missing piece in the whole Java EE jigsaw seen from the web perspective. What I like most is that such an approach aims to simplify both design and development of Java EE web applications without loosing its strengths.

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT