BT

Gavin King Provides Web Beans Preview (JSR 299) Featuring Guice Inspired Dependency Injection

| by Scott Delap Follow 0 Followers on Sep 24, 2007. Estimated reading time: 2 minutes |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Gavin King has released a 4 part preview (one, two, three, four) of the upcoming Web Beans (JSR 299) specification. Web Beans was initiated by JBoss to fill a gap in JEE 5 involving the web tier and transactional tier. Members of the JSR include Sun, Oracle, and Google. King states that the component model is deeply influenced by Google Guice and Seam.

The first article in the series provides an introduction to the technology:

...Web Beans is a component model that is compatible with technologies in both tiers. Web Beans integrates with both JSF and EJB3, allowing an EJB3 session bean to act as a JSF managed bean, thus unifying the two component models. Additionally, Web Beans provides a conversation model and persistence context management, thereby solving state management problems and optimistic transaction management problems that affect JSF and JPA...A Web Bean is an application component containing business logic. A Web Bean may be called directly from Java code, or it may be invoked via Unified EL. A Web Bean may access transactional resources. Dependencies between Web Beans are managed automatically by the Web Beans container. Most Web Beans are stateful and contextual. The lifecycle of a Web Bean is always managed by the container...

The second article in the series covers the injection, binding annotations, and component types of the specification. Supported injection types are:

  • Direct Field
  • Method
  • Constructor
  • Parameter

The third article in the series provides examples of declaring components via XML instead of annotations. Finally King covers scopes, contexts, and resolver methods. With available scope types as follows:

  • @RequestScoped
  • @SessionScoped
  • @ApplicationScoped
  • @ConversationScoped

Expectedly such a large amount of content has created a similar amount of commentary. One of the more interesting observations is:

There's been a lot of talk over the past few years that perhaps Interface 21 should push to formally make the Spring Framework a part of the JEE specs -- it seemed like it might be possible with Rod Johnson officially declaring his support for JEE 6... well it looks like "Crazy" Bob Lee and the team behind Guice may have found a back door to get themselves into the party first -- according to a new series of articles about the upcoming Web Beans, the new spec is actually influenced by a combination of Seam and Guice ... I find these articles interesting in that Google has apparently taken the JBoss approach to supporting the JCP -- that is, create an independent product to fill a whole in the JEE specs, and then use the JCP to make that product into a spec itself (take a look at the JPA for a previous example)...

Similar comments can be found with the articles themselves:

Interesting - the tie in to Seam is obvious, but this is the first I've seen of any involvement from the Guice team... I can't help but wonder if the term 'Web Beans' is accurate...

To which King replies:

Probably, Seam will eventually be split into two layers. 1) The core component engine, which will evolve into the Web Beans RI 2) The framework layer which will provide all the built-in components, JSF components, etc ... Bob has contributed a huge amount of effort and ideas to the specification.

Rate this Article

Adoption Stage
Style

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.

Tell us what you think

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

Email me replies to any of my messages in this thread

Ummm, Seam was around ages before Guice, not to mention a gazillion others by gcom nz

Seems like some writers / editors hit post before fact-checking. Someone just outta college or sumthin?!? ;-D

Re: Ummm, Seam was around ages before Guice, not to mention a gazillion oth by Floyd Marinescu

Seems like some writers / editors hit post before fact-checking. Someone just outta college or sumthin?!? ;-D

Hi gcom nz, first of all, would you please update your preferences with your real name? We'd like InfoQ to be a place for serious discussion. Second, please note that it was Gavin who said that web beans was influenced by Guice, in part 1 of his blog series, Gavin said: "The component model is deeply influenced by Google Guice and Seam."

thanks,

Floyd

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

Email me replies to any of my messages in this thread

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

Email me replies to any of my messages in this thread

2 Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT