Java SE: Exploiting Modularity and Other New Features Ed 1.1 — Lesson 4: Modern APIs, Tooling, Security, Performance, and Upgrade Readiness

Technical Scope

• HTTP Client, date and time, process API, files, and utility enhancements
• JShell, compiler and runtime options, diagnostics, Flight Recorder awareness
• security changes, removed or deprecated APIs, illegal access, and dependencies
• upgrade checklist, performance baseline, deployment image, and modernization runbook

Instructor Demonstration

Demonstrate HTTP Client, date and time, process API, files, and utility enhancements 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 JShell, compiler and runtime options, diagnostics, Flight Recorder awareness and security changes, removed or deprecated APIs, illegal access, and dependencies, then test a failure, exception, or business-control scenario involving upgrade checklist, performance baseline, deployment image, and modernization runbook.

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 Modern APIs, Tooling, Security, Performance, and Upgrade Readiness 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 HTTP Client, date and time, process API, files, and utility enhancements, JShell, compiler and runtime options, diagnostics, Flight Recorder awareness, security changes, removed or deprecated APIs, illegal access, and dependencies, or upgrade checklist, performance baseline, deployment image, and modernization runbook 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 Modern APIs, Tooling, Security, Performance, and Upgrade Readiness and defend the result with documented evidence.