Java EE Services for Spring Applications
summary
Analysis of Spring 3.1/3.2 integration with Java EE6 shows concrete options: use server-managed persistence units (or local EMF) to share persistence context with EJBs, choose JTA versus local transactions (JTA is necessary for true XA multi‑resource commits), plug into servlet 3.0 async for Spring MVC callables, or use a JCA listener container for heavy JMS. Demonstrations include Arquillian in-container tests (fast server boot and real deployments) and DeltaSpike/Seam3–based CDI ↔ Spring bean bridging; Spring 3.3 targets Java EE7 APIs.
AI-written summary · about
chapters (20)
- 0:00Introductions and Overview
- 2:58Programming Model vs Services
- 5:48Spring's Role in Environments
- 8:51Java EE Services Overview
- 12:27Managed Data Sources
- 16:03JTA Transaction Management
- 22:57XA Transactions and Recovery
- 27:34Service Trade-offs and Best Practices
- 34:05Configuring Transaction Managers
- 35:34Persistence Context Management
- 45:37JMS and JCA Integration
- 48:48Advanced Messaging Scenarios
- 52:32Servlet and Bean Validation
- 56:40Java EE 7 and Standardization
- 59:38Caching (JSR 107) and WebSockets
- 1:04:31Concurrency and Future Specs
- 1:07:09In-Container Testing with Arquillian
- 1:09:32Arquillian Spring Extension
- 1:13:30Spring and CDI Integration
- 1:21:43Conclusions and Q&A
