FREE & OPEN SOURCE · JAVA 17+

Make the edit.
Keep the server warm.

Reload supported Java, Spring and SAP Commerce changes in your running application, with a clear path when a restart is needed.

  1. Edit a method in your application.
  2. Build it into a watched output.
  3. Use the changed behaviour in the running app.
See your first reload

What you can change
without restarting

Start with the edits you make every day. The badges come directly from the reload matrix; each link explains the conditions and next step.

Reloads

Edit an existing method body

Method-body edits reload when compiled into a watched output. Existing object fields stay in place on the JVM-only path. A separate framework refresh can recreate beans.

Conditions and next step
Reloads, with a condition

Add or remove a method

Added or removed methods work through hot-compiled callers on a stock JDK. They are not native members of the original Class. A caller using a removed method gets NoSuchMethodError, or the inherited implementation for a removed override, as after restart.

Conditions and next step
Reloads, with a condition

Refresh an affected singleton bean

Supported singleton paths recreate the affected bean and repair supported references. Mutable state can reset. Arbitrary external holders are not repaired.

Conditions and next step
Reloads, with a condition

Add/change a controller endpoint

Supported mapping rescans discover changed endpoints, including added methods on a stock JVM. Receiver, metadata and classloader restrictions still apply.

Conditions and next step
Reloads, with a condition

Edit recognized Boot properties

Recognized Boot properties are checked for binding, conversion and validation before live mutation. Invalid or uncheckable input stays pending. Setter or recreation failure can partially apply.

Conditions and next step
Reloads, with a condition

Save *-items.xml / *-beans.xml

Platform generation and builds can reload the generated classes. Persistence, type-system updates and native reflection are separate requirements.

Conditions and next step

Redefines classes in the running JVM via the Instrumentation API. Method body changes apply in ~50ms. Zero downtime.

Explore all changes and restart boundaries

Built for the
SAP Commerce loop

Save items.xml or beans.xml to run platform generation and reload the generated classes within the documented scope. Keep schema changes separate: a new database column still needs an update.

The default live suite defines 64 required scenarios. The guide explains Java edits, configuration, interceptor refresh and opt-in ImpEx import.

Set up SAP Commerce

Choose the workflow
that fits your project

An in-place reload and a development restart solve different problems. Compare the common paths, then read the full scope and sources.

Compare the development workflow
CapabilityReclazzJRebelSpring Boot DevToolsHotswapAgent / DCEVM
Price and licenceFree, Apache 2.0 SourceCommercial; price by quote SourceFree, Apache 2.0 (part of Spring Boot) SourceFree, GPL-2.0 Source
How a change is appliedRedefines classes in the running JVM SourceReloads classes in the running JVM SourceRestarts the application in a fresh classloader SourceRedefines classes in the running JVM Source
What survives a changeMethod edits keep object fields; a refreshed Spring bean is recreated and can reset its state SourceExisting instances kept; added fields are not initialized in them SourceApplication state resets with the application classloader (inferred from restart mechanism) SourceJVM keeps running; object state not described
Add or remove methods and fields on a stock JDKYes on supported JDK 17+ paths, through hot-compiled callers; new members are not visible to plain reflection SourceClass structure changes on standard JVMs; vendor article describes the mechanism SourcePicked up by a restart SourceNeeds an enhanced JVM such as JetBrains Runtime (DCEVM) Source
SAP Commerce: items.xml / beans.xml changeRegenerates and reloads model/DTO classes; schema update still separate SourceNot documentedNot documentedNot documented

Not documented means the reviewed vendor documentation does not establish the capability. It does not mean the product cannot do it.

Read the full comparison and sources

One agent.
A shorter feedback loop.

A Java agent runs inside your application JVM and watches compiled output. It applies supported class changes and coordinates framework refreshes. Your application stays running while you check the result.

Method edits keep existing object fields on the JVM-only path. A refreshed bean starts fresh; changing a superclass needs a restart.

Understand Java and JVM limits

Agent target: Java 17+. Baseline tests: 17/21; JDK 25 runtime tested locally. IntelliJ plugin: 2023.3 to 2026.2.

Check versions and requirements

Your first reload
in three steps

Use one attachment route for each JVM. Start with IntelliJ, or follow the quickstart for Gradle, Maven and a standalone agent.

01

Install and enable

Install the Reclazz IntelliJ plugin. Enable Reclazz for your run configuration; for SAP Commerce, follow the platform setup.

02

Start and wait

Start your application with the agent attached. Wait for the default 30-second startup delay before making your first change.

03

Build and check

Change a method body and build it into the watched output. Call it again and check the result; the quickstart shows what success looks like.

Follow the quickstart

Before your first reload

Which changes can I reload?

Start with a method-body edit. Added methods, Spring beans, endpoints, properties and SAP generated classes have documented conditions. Check the reload matrix before a larger change.

Will my application state survive?

Method-body edits keep existing object fields on the JVM-only path. A refreshed Spring bean is destroyed and recreated, so its mutable state can reset.

Do I need a special JVM?

Supported structural changes work on stock JDK 17+ through hot-compiled callers. Plain reflection cannot see added members on that path. JetBrains Runtime or DCEVM provides enhanced redefinition; a superclass change still needs a restart.

What happens after an items.xml save?

Reclazz runs platform generation and reloads the generated classes within the documented SAP scope. A new database column still needs a schema update. Follow the SAP Commerce guide for setup and opt-ins.

Can I use Gradle or Maven instead of IntelliJ?

Yes. Attach the agent through one launcher: IntelliJ, the Gradle plugin, Maven or a standalone Java command. Build your edit into a watched output and verify the changed application behaviour.

A change did not reload? Start here.

Search guides, changes and limits. Your query stays in this browser.

↑ ↓ to select · Enter to open · Esc to close