Jakarta EE From Zero

Learn the enterprise Java standard that runs a huge share of big-company backends: what Jakarta EE actually is (specs vs app servers), CDI dependency injection, JAX-RS REST APIs, Jakarta Persistence, JTA transactions, validation and JSON binding, enterprise beans and messaging, security, and the cloud-native MicroProfile direction.

1. What Jakarta EE Is Jakarta EE is a set of standard enterprise Java APIs that vendors implement; you code to the spec and a server provides the engine. Covers the specs, the javax-to-jakarta rename, and how it differs from Spring.
2. The Application Server & Deployment How classic Jakarta EE runs: your app deploys INTO a running application server that provides the specs. WAR/EAR packaging, app server vs servlet container, and the modern self-contained shift.
3. CDI: Contexts & Dependency Injection CDI is Jakarta EE's standard dependency-injection container: @Inject wires beans, scopes manage lifecycle, qualifiers pick implementations, and producers/interceptors extend it — the backbone every other spec plugs into.
4. JAX-RS: Building REST APIs Expose your CDI beans over HTTP the standard way: an @ApplicationPath bootstrap, @Path resource classes, the HTTP-method annotations, path and query params, JSON-B binding, and Response for honest status codes.
5. Jakarta Persistence (JPA) JPA inside a Jakarta EE container: the persistence unit and persistence.xml, the container-injected @PersistenceContext EntityManager, and how Hibernate fits under it all.
6. Transactions with JTA How the Jakarta EE container runs transactions for you: declarative @Transactional on a CDI bean, what JTA coordinates, transaction attributes, the checked-exception rollback trap, and how it all scopes the persistence context.
7. Validation & JSON Binding Reject bad input at the door with Jakarta Bean Validation, control object-to-JSON mapping with JSON-B, and see how @Valid, JSON-B, CDI, and JPA fit into one request flow.
8. Enterprise Beans & Messaging Enterprise beans (EJB) give you pooling, transactions, scheduling, and async for free; Jakarta Messaging lets services hand work to each other through queues — the enterprise way to stay loosely coupled.
9. Jakarta Security Secure your Product REST API the standard way: an HttpAuthenticationMechanism proves who you are, an identity store validates credentials, and @RolesAllowed decides what you can do — with JWT for stateless APIs.
10. MicroProfile & Where to Go Next You can build a standard Jakarta EE service end to end. Now meet MicroProfile, the runtimes like Quarkus and Helidon, where this fits in a career, and what to build next.