Training course · Claude Code · Java & Spring

Claude Code for Java and Spring Developers

Agentic coding with Claude Code in the terminal and IDE: CLAUDE.md, subagents, hooks, MCP, CI pipelines and secure permissions.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

“Claude Code for Java and Spring Developers” is designed for roles such as Java back-end developers using Spring Boot or Jakarta EE, Teams modernising legacy Java applications and Software architects for enterprise and microservice landscapes and shows step by step how to use Claude Code productively, safely and transparently in Java & Spring – from the fundamentals to advanced workflows.

Claude Code is Anthropic’s agentic coding assistant, working directly in your terminal and in popular IDEs. Rather than completing individual lines, it reads your repository, plans changes across multiple files, runs commands, executes tests and prepares commits. Over two days you will learn to use it with deliberate control: clear project instructions in CLAUDE.md, careful context management, and a workflow in which you set the direction as a developer and can trace every change the agent makes back to a clear intention.

The course is built around real engineering work: diagnosing bugs, delivering features, refactoring legacy code and filling gaps in test coverage. You will configure subagents for specialised tasks, enforce quality checks with hooks, connect external systems through the Model Context Protocol (MCP) and capture team knowledge as reusable skills. Finally, you will run Claude Code headless in CI pipelines and define permissions, sandboxing and approval rules so that its use remains defensible even in security-sensitive environments.

Java and Spring carry business-critical systems in many organisations: banking back ends, ERP integrations, public-sector applications and large microservice estates. These systems have often grown over many years, and modernisation never stops. AI coding assistants and agents change the heaviest routine work in particular: major Spring Boot upgrades including the javax-to-jakarta switch, JUnit and Mockito tests for poorly covered code, refactorings towards records and modern language features, and analysis of stack traces and Hibernate issues. Clear guardrails are essential: build tool, module structure, architecture rules and test strategy all need to be in context. This course shows you how to use agents productively and in a controlled way in Maven or Gradle projects.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • Java back-end developers using Spring Boot or Jakarta EE
  • Teams modernising legacy Java applications
  • Software architects for enterprise and microservice landscapes
  • Developers in banking, insurance and the public sector
  • Tech leads responsible for upgrades and technical debt

Typical challenges we address

  • Laborious framework and JDK upgrades with numerous breaking changes
  • Large legacy codebases with low test coverage and tight coupling
  • Hard-to-analyse performance issues in JPA, Hibernate and transactions
  • Heavy boilerplate in configuration, mapping and interface code

What you will be able to do

  • You use Claude Code for multi-step development tasks while keeping full control over every change.
  • You maintain a CLAUDE.md that effectively conveys project conventions, commands and architectural guidance to the agent.
  • You extend Claude Code with subagents, hooks, MCP servers and skills tailored to your team.
  • You integrate Claude Code into Git workflows and CI pipelines with traceable, test-backed results.
  • Use AI agents for Spring Boot upgrades, refactorings and test generation in Maven and Gradle projects.
  • Diagnose Hibernate, performance and production issues faster with AI support.
  • Embed architecture rules and quality standards so that generated Java code adheres to them reliably.

Course outline

Day 1

Module 1 How Claude Code works
  • Installation, sign-in and use in the terminal, VS Code and JetBrains IDEs
  • Understanding the agentic loop: read, plan, act, verify
  • Using plan mode to agree on an approach before any code changes
  • Writing effective task briefs with goal, context and acceptance criteria
Module 2 Project context with CLAUDE.md and context management
  • Structuring CLAUDE.md at project, directory and user level
  • Documenting build, test and style conventions so the agent follows them reliably
  • Managing the context window with targeted file references, compaction and fresh sessions
  • Resuming sessions and breaking long tasks into manageable stages
Module 3 Extending Claude Code with subagents, hooks, MCP and skills
  • Defining subagents for code review, research or test generation
  • Using hooks to enforce formatting, linting or checks before and after tool calls
  • Connecting MCP servers for issue trackers, databases or internal documentation
  • Creating custom slash commands and skills for recurring team workflows
Module 4 Git workflows, testing and quality assurance
  • Creating branches, meaningful commits and pull requests with Claude Code
  • Test-first work: have tests written before the implementation
  • Reviewing diffs systematically and rejecting or refining changes
  • Organising parallel work with Git worktrees and multiple sessions

Day 2

Module 5 Headless operation, CI and security
  • Running Claude Code non-interactively in scripts and CI pipelines
  • Automated reviews and issue handling in GitHub or GitLab workflows
  • Configuring permission modes, allow and deny rules, and sandboxing
  • Handling secrets, prompt injection risks and organisation-wide policies
Module 6 Practice lab: Java & Spring
  • Driving a Spring Boot upgrade
  • Generating JUnit and Mockito tests
  • Refactoring legacy code
  • Analysing JPA and Hibernate issues
  • REST APIs and interfaces
  • Making sense of stack traces and production errors
Module 7 Data protection, quality & transfer to daily work
  • Java systems often run in regulated sectors: agree with information security and data protection which code may be sent to external models, and take requirements such as DORA, NIS2 or national banking IT rules into account. Generated code and new Maven dependencies should be checked for licences and known vulnerabilities and recorded in an SBOM.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Driving a Spring Boot upgrade

The agent analyses dependencies, applies OpenRewrite recipes, switches javax packages to jakarta, adapts deprecated configuration and security setups and iterates over build and tests until the application is green again.

Generating JUnit and Mockito tests

Services and controllers get unit tests with JUnit and Mockito plus slice tests using WebMvcTest or DataJpaTest. The AI deliberately raises coverage on critical paths and documents test assumptions.

Refactoring legacy code

Large classes are split up, DTOs turned into records, null checks replaced with Optional and streams used where they help. Existing tests safeguard behaviour at every step.

Analysing JPA and Hibernate issues

The AI reads SQL logs and stack traces, spots N+1 queries, LazyInitializationExceptions and poor fetch strategies, and proposes entity graphs, projections or index changes. Each optimisation is backed by SQL logs.

REST APIs and interfaces

OpenAPI specifications are turned into controllers, DTOs, MapStruct mappers and Bean Validation, complete with consistent error handling via ControllerAdvice and integration tests. Existing package and naming conventions are respected.

Making sense of stack traces and production errors

Long stack traces, thread dumps and log excerpts are summarised, the likely root cause is narrowed down and a reproducing test case plus fix is proposed.

Possible hands-on projects

Spring Boot microservice

A REST service with Spring Data JPA, Flyway migrations, Bean Validation, Actuator endpoints and Testcontainers tests, developed entirely by an AI agent from a specification.

Dependency report for Maven and Gradle

A command-line tool that analyses build files, lists outdated and vulnerable libraries and describes upgrade paths along with expected breaking changes.

Architecture rule checks

An ArchUnit test suite that automatically enforces your project’s layering rules, package dependencies and naming conventions and runs in the CI pipeline.

Prerequisites

You have hands-on programming experience in at least one language and are comfortable with Git and the command line. In-depth Java knowledge and practical experience with Spring Boot or Jakarta EE, Maven or Gradle and Git.

Technical requirements

Your own laptop with admin rights, Git, a Node.js runtime and an up-to-date editor; a Claude subscription or Anthropic API access is required for the exercises.

Data protection & compliance

Java systems often run in regulated sectors: agree with information security and data protection which code may be sent to external models, and take requirements such as DORA, NIS2 or national banking IT rules into account. Generated code and new Maven dependencies should be checked for licences and known vulnerabilities and recorded in an SBOM.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Tue, 24 November 2026 – Wed, 25 November 2026 Online Request
  • Mon, 30 November 2026 – Tue, 1 December 2026 Munich Request
  • Wed, 9 December 2026 – Thu, 10 December 2026 Online Request
  • Thu, 7 January 2027 – Fri, 8 January 2027 Online Request
  • Thu, 14 January 2027 – Fri, 15 January 2027 Hanover Request
  • Mon, 18 January 2027 – Tue, 19 January 2027 Online Request

Frequently asked questions

How is Claude Code different from traditional code completion?

Code completion suggests the next few lines, whereas Claude Code acts as an agent that handles whole tasks: it searches the repository, plans changes across several files, runs tests and commands, and corrects itself based on the results. You define the goal and review the outcome instead of steering every single line yourself.

Is Claude Code secure enough for enterprise use?

By default, Claude Code asks for approval before editing files or running commands. Permission rules, sandboxing, managed settings and hooks let you define precisely what the agent may do. During the course you learn to configure these mechanisms to match your security and data protection requirements and to assess risks such as prompt injection.

Does Claude Code work with my language and tech stack?

Yes. Claude Code is language-agnostic because it works with files, terminal commands and your existing build and test tooling. Whether you use Python, Java, TypeScript, Go, SAP-related code or infrastructure as code, what matters most is a well-written CLAUDE.md describing your commands and conventions. Each course variant adds the relevant domain focus.

Can an AI agent carry out a major Spring Boot upgrade on its own?

An agent can take on much of the mechanical work – package switches, configuration changes and iteratively fixing compile and test failures – especially when combined with OpenRewrite. Architecture decisions, functional sign-off and testing in realistic environments remain the team’s job. On the course you practise this workflow on a sample project.

Is AI-assisted coding allowed in regulated environments?

In principle yes, but with clear rules. What matters is the choice of provider and operating model, contractual commitments on data use, approval processes and traceable reviews. We discuss how banks, insurers and public authorities typically approach this and which questions you should settle with your information security team.

How much does “Claude Code for Java and Spring Developers” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for Java and Spring Developers

More Claude Code courses

All 77 Claude Code courses

Claude Code · MunichClaude Code · SalzburgClaude Code · BerlinClaude Code · AugsburgClaude Code · HanoverClaude Code · BremenClaude Code · StuttgartClaude Code · KaiserslauternClaude Code · Online