You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes in @EventData value are not applied after server restart, when I use JRebel for live-reload.
As a developer, I want to immediately see the changes in event data, e.g. if I want to rename the event.detail parameter from @EventData("event.detail.position") to @EventData("event.detail.coordinate") and have a working Java event handling without full server restart or browser page refresh.
Expected behavior
Changes to event data are applied immediately after server reload, this is how it works when using HotswapAgent.
However, with JRebel it requires a page refresh or server restart.
Minimal reproducible example
Change event.detail.coordinate to e.g. event.detail.coordinate111
Start the project with JRebel
Open localhost:8080
Move the marker to other place on the map component
Notice an exception in server logs and no pop up message
Change the param name to event.detail.coordinate, save the file, wait for class reload
Description of the bug
Changes in
@EventData
value are not applied after server restart, when I use JRebel for live-reload.As a developer, I want to immediately see the changes in event data, e.g. if I want to rename the event.detail parameter from
@EventData("event.detail.position")
to@EventData("event.detail.coordinate")
and have a working Java event handling without full server restart or browser page refresh.Expected behavior
Changes to event data are applied immediately after server reload, this is how it works when using HotswapAgent.
However, with JRebel it requires a page refresh or server restart.
Minimal reproducible example
event.detail.coordinate
to e.g.event.detail.coordinate111
event.detail.coordinate
, save the file, wait for class reloadProject example
event-data-jrebel.zip
Versions
JRebel Agent 2024.4.2-SNAPSHOT (2024-11-21 11:38)
The text was updated successfully, but these errors were encountered: