Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343559 - JEM needs to handle a flush better
Summary: JEM needs to handle a flush better
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.jem (show other bugs)
Version: 1.5.5   Edit
Hardware: PC Windows XP
: P2 major (vote)
Target Milestone: 3.0.5 P   Edit
Assignee: Carl Anderson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on: 343558
Blocks: 348221 348396
  Show dependency tree
 
Reported: 2011-04-21 10:44 EDT by Carl Anderson CLA
Modified: 2011-06-06 10:07 EDT (History)
0 users

See Also:
cbridgha: review+

Attachments
Keep the current Methods "valid" (2.68 KB, patch)
2011-04-21 11:03 EDT, Carl Anderson CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Anderson CLA 2011-04-21 10:44:51 EDT 
We need to get this fix into WTP 3.0.5 P, too.

+++ This bug was initially created as a clone of Bug #343558 +++

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.
Comment 1 Carl Anderson CLA 2011-04-21 11:03:21 EDT 
Created attachment 193844 [details]
Keep the current Methods "valid"
Comment 2 Chuck Bridgham CLA 2011-04-22 15:27:57 EDT 
approved
Comment 3 Carl Anderson CLA 2011-04-22 17:17:38 EDT 
Committed to R3_0_5_patches