★ wanayoo — archive 1999 http://blogs.oracle.com/java/tags/CDINouvelle recherche | Portail wanayoo

Tuesday Apr 12, 2011

Contexts and Dependency Injection in Java EE 6

Java Champion, and Oracle Magazine's "Java Developer of the Year" Adam Bien, begins his precise and clear article, titled "Contexts and Dependency Injection in Java EE 6" by addressing an embarrassment of riches in Java EE 6 that leaves developers with a diverse array of choices:

"Java Platform, Enterprise Edition (Java EE) 5 brought dependency injection (DI) with Convention over Configuration to Enterprise JavaBeans (EJB) 3.0. Java EE 6 introduces the flexible and powerful @Inject dependency injection model (JSR-330 and JSR-299) in addition to the already existing @EJB annotation. So when should you use what?"

Contexts and Dependency Injection (CDI), the new Java EE 6 specification, introduces the concept of "contextual" references or scopes. Managed beans in CDI live in well-defined scope and are created and destroyed on demand by the container. Adam Bien articulates the best ways to qualify and to configure the dependencies using typed annotations, known as "qualifiers" with optional attributes instead of plain strings.

All in all, Bien gives us a detailed understanding of an important step forward in Java EE. See the story here.

Friday Jan 07, 2011

Technical Article: Oracle Magazine Java Developer of the Year Adam Bien on Java EE 6 Simplicity by Design

Java Champion and Oracle Magazine Java Developer of the Year, Adam Bien, offers his unique perspective on how to leverage new Java EE 6 features to build simple and maintainable applications in a new article in Oracle Magazine. Bien examines different Java EE 6 architectures and design approaches in an effort to help developers build efficient, simple, and maintainable applications.

From the article:

"Java EE 6 consists of a set of independent APIs released together under the Java EE name. Although these APIs are independent, they fit together surprisingly well. For a given application, you could use only JavaServer Faces (JSF) 2.0, you could use Enterprise JavaBeans (EJB) 3.1 for transactional services, or you could use Contexts and Dependency Injection (CDI) with Java Persistence API (JPA) 2.0 and the Bean Validation model to implement transactions."

"With a pragmatic mix of available Java EE 6 APIs, you can entirely eliminate the need to implement infrastructure services such as transactions, threading, throttling, or monitoring in your application. The real challenge is in selecting the right subset of APIs that minimizes overhead and complexity while making sure you don't have to reinvent the wheel with custom code. As a general rule, you should strive to use existing Java SE and Java EE services before expanding your search to find alternatives."

Read the entire article here.

Friday Dec 17, 2010

The 2010 JavaOne Java EE 6 Panel: Where We Are and Where We're Going

An informative article, based on a 2010 JavaOne (San Francisco, California) panel session, surveys a variety of expert perspectives on Java EE 6.

The panel, moderated by Oracle's Alexis Moussine-Pouchkine, consisted of:

* Adam Bien, Consultant Author/ Speaker, adam-bien.com
* Emmanuel Bernard, Principal Software Engineer, JBoss by Red Hat,
* David Blevins, Senior Software Engineer, and co-founder of the OpenEJB project and a     founder of Apache Geronimo
* Roberto Chinnici, Technical Staff Consulting Member, Oracle
* Jim Knutson, Java EE Architect, IBM
* Reza Rahman, Lead Engineer, Caucho Technology, Inc.,
* Krasimir Semerdzhiev, Development Architect, SAP Labs Bulgaria

The panel addressed such topics as Platform and API Adoption, Contexts and Dependency Injection (CDI), Java EE vs. Spring, the impact of Java EE 6 on tooling and testing, Java EE.next, along with a variety of audience questions.

Read the entire article for the whole picture.

About
Search
Categories
Archives
« May 2011
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
11
13
14
15
16
18
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today
Menu
Feeds