Begins by laying out the differences in the dependency injection strategy between Seam 2 and CDI. Then explains how proxies work in CDI and how to leverage a non-portable Weld feature to optimize the behavior of the proxy.
This tip of the day briefly describes the event mechanism in CDI. A basic event/observer is shown, then several qualified events with matching observers.
So Java EE 6 is out, and you've decided to give it a go. You're trying to port an existing application over to the new stack (or are trying to create a new one for the first time,) but exceptions are bursting through the seams and you just can't seem to get things to work. If you're familiar with Spring and Hibernate (with all the joy that is OpenSessionInView or OpenSessionInConversation,) more than likely the problems you're having are related to the Java Persistence API (JPA), combined with Enterprise Java Beans (EJB). Contexts and Dependency Injection (CDI) should be a familiar face if coming from Spring, but things are subtly different in the world of Java EE.
This article highlights why the EJB 3.1 and CDI programming models form an ideal pairing for creating lightweight enterprise applications. The individual feature sets of both specifications are clearly presented. The article goes on to show how these feature sets complement one another, filling in gaps that the other doesn't address. Simple companion source code is provided.
Group items tagged 
