Enhanced Class Redefinition JEP
jon.masamitsu at oracle.com
Fri Jul 29 10:29:20 PDT 2011
From the JEP Description section
"The behavior of the current mechanism that swaps method bodies is
As I recall some of the class redefinition in your implementation requires
doing a heap iteration (scan and update similar to a full GC)
to update references to redefined classes.
Does the statement above from the description mean that in your
implementation the swapping method bodies does not require the
heap iteration? I think the current implementation in hotspot does
not require such an iteration.
On 7/27/2011 3:03 PM, Thomas Wuerthinger wrote:
> Hi all,
> find attached a JDK Enhancement-Proposal (JEP) for enhancing HotSpot's
> class redefinition capabilities. The proposed features include
> adding/removing methods and fields as well as adding supertypes. The
> JEP includes links to a prototype implementation and technical
> publications about the approach.
> Thomas Wuerthinger
More information about the hotspot-dev