Community
Participate
Working Groups
Currently, if JEM is gathering (or has gathered) the Methods from a (JEM) JavaClass, and a flush() occurs, the Methods are removed from their parents and are invalid, resulting in NPEs and other errors without any warning. There are things we can do, such as replacing the parent JavaClass with a JavaClassRef, that will at least keep the current Methods useful, while still allowing the flush to proceed.
Created attachment 193836 [details] Keep the current Methods "valid"
This is causing (intermittent) major problems, including unnecessary termination, of various "headless" utilities based on WTP.
approved
Created attachment 197303 [details] Keep the current Methods "valid", and add a null check
Created attachment 197305 [details] Keep the current Methods "valid", and add a null check Removed extraneous (and accidentally included) System.out.println() calls.
Committed to R1_5_5_patches