AD183 Red Hat Application Development I: Programming in Java EE — Lesson 1: Java EE Architecture, Maven, CDI, Dependency Injection, and Application Structure

Learning Objectives

• Interpret the architecture, dependencies, and expected behavior of Java EE architecture, Maven, and CDI.
• Apply dependency injection and application structure while preserving reviewable technical evidence.
• Recognize and correct the risk where a hidden prerequisite causes the first configuration step to produce an incomplete result.

Detailed Topics

• Java EE architecture: apply the concept to a Java team building and deploying a maintainable enterprise application on Red Hat JBoss EAP, record the relevant settings or decisions, and explain the operational consequence.
• Maven: apply the concept to a Java team building and deploying a maintainable enterprise application on Red Hat JBoss EAP, record the relevant settings or decisions, and explain the operational consequence.
• CDI: apply the concept to a Java team building and deploying a maintainable enterprise application on Red Hat JBoss EAP, record the relevant settings or decisions, and explain the operational consequence.
• dependency injection: apply the concept to a Java team building and deploying a maintainable enterprise application on Red Hat JBoss EAP, record the relevant settings or decisions, and explain the operational consequence.
• application structure: apply the concept to a Java team building and deploying a maintainable enterprise application on Red Hat JBoss EAP, record the relevant settings or decisions, and explain the operational consequence.

Instructor Demonstration

The instructor demonstrates java ee architecture, maven, cdi, dependency injection, and application structure by tracing the relevant architecture, commands, configuration, messages, and evidence. The walkthrough highlights how a hidden prerequisite causes the first configuration step to produce an incomplete result and shows how to isolate the cause without masking dependent issues.

Hands-On Exercise

Build a baseline and capture the initial state for Java EE Architecture, Maven, CDI, Dependency Injection, and Application Structure. Add verified outcomes to the Java EE application repository, integration tests, deployment package, and developer handover guide.

1. Confirm the scope, versions, access, dependencies, and success criteria.
2. Perform the workflow while recording commands, settings, output, and platform events.
3. Test one expected case and one controlled exception specific to this lesson.
4. Retest the correction and document ownership, rollback, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences Java EE architecture in the stated scenario.
• Compare two approaches for dependency injection and explain the security, reliability, and support trade-offs.
• Decide what evidence must be retained in the Java EE application repository, integration tests, deployment package, and developer handover guide before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check architecture, access, dependencies, and starting conditions separately, then correlate logs, events, commands, and configuration history. Do not accept the initial assumption that a hidden prerequisite causes the first configuration step to produce an incomplete result; confirm the cause with a reproducible retest.

Validation Checklist

• The required architecture, access, dependencies, and starting conditions were checked and recorded.
• The normal path and a course-specific exception were tested.
• The Java EE application repository, integration tests, deployment package, and developer handover guide links conclusions to commands, configuration, logs, or other objective evidence.
• Corrective actions, rollback steps, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Java EE Architecture, Maven, CDI, Dependency Injection, and Application Structure, explain the observed Red Hat platform behavior, and support the result with a reviewable Java EE application repository, integration tests, deployment package, and developer handover guide.