Adam Bien "EJB 3.1..." Part 5

### Overview In this talk, Adam Bien discusses Enterprise JavaBeans (EJB) configuration, migration strategies, and developer workflow across EJB 2, EJB 3.0, and EJB 3.1. Addressing common criticisms regarding EJB complexity, the session focuses on debunking myths about configuration verbosity, simplifying migration from legacy EJB 2 architectures, and demonstrating how minimal modern EJB implementations can be.

### Key Topics - **Configuration Precedence:** How conventions, Java annotations, and XML deployment descriptors interact, highlighting the ability to override configurations per environment. - **Dependency Injection and Alternatives:** Injecting primitive data types, limitations in EJB 3, upcoming changes in EJB 3.1, and using frameworks like Guice (Juice) or databases for bean configuration. - **Spring Integration:** Mention of SpringSource's Pitchfork container providing EJB 3.0 support and project Matisse bringing EJB 3.1 support. - **EJB 2 to EJB 3 Migration:** Overcoming legacy J2EE 1.4 XML dependencies, leveraging backward compatibility, replacing service locators, and using annotations like `@LocalHome`. - **Vendor Neutrality:** The strategic and financial motivations driving companies away from proprietary application servers due to licensing costs. - **Minimal EJB Development:** The development simplicity of modern stateless session beans without deployment descriptors or complex build tooling.

### Technical Details - **Configuration Hierarchy:** EJB relies first on conventions (predefined defaults), which can be overridden by Java annotations. Annotations can further be overridden by XML deployment descriptors. Bien demonstrates using XML strictly for testing overrides and omitting it in production. - **XML and Injection Improvements:** EJB 3 allows configuring and injecting primitive types via XML, though it requires specifying an injection target. In EJB 3.1, the injection target becomes optional or can be removed, reducing verbosity. - **Migration Strategy:** Migrating directly between J2EE 1.4 platforms is complicated by XML configurations. Because EJB 3 is backward compatible with EJB 2, developers can deploy EJB 2 beans in an EJB 3 container. By using annotations such as `@LocalHome`, teams can eliminate XML deployment descriptors, remove legacy service locators via dependency injection, and preserve underlying business logic. Once migrated, teams can incrementally refactor, replacing home interfaces with business interfaces and removing up to 80% of legacy boilerplate code. - **Modern EJB Simplicity:** The simplest modern EJB requires only a class with a default constructor annotated with `@Stateless`. Compiling requires only the stateless annotation on the classpath, packaging into a standard JAR, and dropping it into an application server like GlassFish or JBoss for auto-deployment, without requiring deployment descriptors or code generation wizards.

### Takeaways - EJB 3.x simplifies enterprise Java by prioritizing convention over configuration and making XML completely optional. - Backward compatibility allows safe, incremental modernization of legacy EJB 2 systems while maintaining enterprise vendor independence. - Modern stateless session beans offer a lightweight, boilerplate-free alternative that can be packaged and auto-deployed into standard application servers or integrated within Spring environments.