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 stepFREE & OPEN SOURCE · JAVA 17+
Reload supported Java, Spring and SAP Commerce changes in your running application, with a clear path when a restart is needed.
YOUR NEXT CHANGE
Start with the edits you make every day. The badges come directly from the reload matrix; each link explains the conditions and next step.
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 stepAdded 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 stepSupported singleton paths recreate the affected bean and repair supported references. Mutable state can reset. Arbitrary external holders are not repaired.
Conditions and next stepSupported mapping rescans discover changed endpoints, including added methods on a stock JVM. Receiver, metadata and classloader restrictions still apply.
Conditions and next stepRecognized 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 stepPlatform generation and builds can reload the generated classes. Persistence, type-system updates and native reflection are separate requirements.
Conditions and next stepRedefines classes in the running JVM via the Instrumentation API. Method body changes apply in ~50ms. Zero downtime.
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 CommerceAn in-place reload and a development restart solve different problems. Compare the common paths, then read the full scope and sources.
| Capability | Reclazz | JRebel | Spring Boot DevTools | HotswapAgent / DCEVM |
|---|---|---|---|---|
| Price and licence | Free, Apache 2.0 Source | Commercial; price by quote Source | Free, Apache 2.0 (part of Spring Boot) Source | Free, GPL-2.0 Source |
| How a change is applied | Redefines classes in the running JVM Source | Reloads classes in the running JVM Source | Restarts the application in a fresh classloader Source | Redefines classes in the running JVM Source |
| What survives a change | Method edits keep object fields; a refreshed Spring bean is recreated and can reset its state Source | Existing instances kept; added fields are not initialized in them Source | Application state resets with the application classloader (inferred from restart mechanism) Source | JVM keeps running; object state not described |
| Add or remove methods and fields on a stock JDK | Yes on supported JDK 17+ paths, through hot-compiled callers; new members are not visible to plain reflection Source | Class structure changes on standard JVMs; vendor article describes the mechanism Source | Picked up by a restart Source | Needs an enhanced JVM such as JetBrains Runtime (DCEVM) Source |
| SAP Commerce: items.xml / beans.xml change | Regenerates and reloads model/DTO classes; schema update still separate Source | Not documented | Not documented | Not 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 sourcesA 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 limitsAgent target: Java 17+. Baseline tests: 17/21; JDK 25 runtime tested locally. IntelliJ plugin: 2023.3 to 2026.2.
Check versions and requirementsUse one attachment route for each JVM. Start with IntelliJ, or follow the quickstart for Gradle, Maven and a standalone agent.
Install the Reclazz IntelliJ plugin. Enable Reclazz for your run configuration; for SAP Commerce, follow the platform setup.
Start your application with the agent attached. Wait for the default 30-second startup delay before making your first change.
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.
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.
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.
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.
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.
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.