Developing Applications for the Java EE 7 Platform Ed 1 — Lesson 2: EJB Transactions, JMS Messaging, and Business Services

Technical Scope

• stateless, stateful, singleton, asynchronous, and timer-service EJB patterns
• container-managed transactions, propagation, rollback, isolation, and exception semantics
• JMS destinations, producers, consumers, message-driven beans, and delivery guarantees
• idempotency, redelivery, poison messages, compensation, and service resilience

Instructor Demonstration

The instructor configures and validates stateless, stateful, singleton, asynchronous, and timer-service EJB patterns, then connects it to container-managed transactions, propagation, rollback, isolation, and exception semantics. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners build and verify an implementation covering container-managed transactions, propagation, rollback, isolation, and exception semantics and JMS destinations, producers, consumers, message-driven beans, and delivery guarantees. The exercise introduces a realistic exception related to idempotency, redelivery, poison messages, compensation, and service resilience and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of JMS destinations, producers, consumers, message-driven beans, and delivery guarantees, traceable proof for stateless, stateful, singleton, asynchronous, and timer-service EJB patterns, and a repeatable recovery path for idempotency, redelivery, poison messages, compensation, and service resilience. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when idempotency, redelivery, poison messages, compensation, and service resilience occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested ejb transactions, jms messaging, and business services implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.