Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Posted by Scott Delap on Sep 24, 2007
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:
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:
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.
Innovation in Your Data Centre
The 5 Mandates of Software Development Teams - Presto Manifesto
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Seems like some writers / editors hit post before fact-checking. Someone just outta college or sumthin?!? ;-D
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
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
2 comments
Watch Thread Reply