Java SE: Exploiting Modularity and Other New Features Ed 1.1 — Lesson 1: Java Platform Module System, Descriptors, Dependencies, and Encapsulation

Technical Scope

• module path versus classpath, named, automatic, and unnamed modules
• module-info.java, requires, exports, opens, uses, and provides
• readability, accessibility, strong encapsulation, and reflective access
• jdeps analysis, dependency graph, split packages, and migration plan

Instructor Demonstration

Demonstrate module path versus classpath, named, automatic, and unnamed modules within a legacy Java application decomposed into explicit modules, upgraded to modern language and API features, tested for compatibility, and packaged for reliable deployment, then capture the exact configuration, command, transaction, report, trace, or code evidence that proves the expected result.

Applied Workshop

Implement a controlled workshop covering module-info.java, requires, exports, opens, uses, and provides and readability, accessibility, strong encapsulation, and reflective access, then test a failure, exception, or business-control scenario involving jdeps analysis, dependency graph, split packages, and migration plan.

1. Confirm the environment, identities, data, dependencies, controls, and expected result.
2. Complete the product-specific configuration, development, analysis, or business-process task.
3. Capture commands, configuration, output, logs, transactions, reports, or test evidence.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

The Java Platform Module System, Descriptors, Dependencies, and Encapsulation result must be reproducible, traceable to approved inputs, and consistent with expected Oracle product or business-process behavior.

• The intended target, scope, and ownership are verified.
• The result is supported by reproducible evidence and expected-value checks.
• Security, performance, reliability, data quality, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance or release.

Failure Analysis

Diagnose issues in module path versus classpath, named, automatic, and unnamed modules, module-info.java, requires, exports, opens, uses, and provides, readability, accessibility, strong encapsulation, and reflective access, or jdeps analysis, dependency graph, split packages, and migration plan without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.

Practical Outcome

Complete a validated implementation or analysis for Java Platform Module System, Descriptors, Dependencies, and Encapsulation and defend the result with documented evidence.