Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343559

Summary:

JEM needs to handle a flush better

Product:

[WebTools] WTP Java EE Tools

Reporter:

Carl Anderson <ccc>

Component:

jst.jem

Assignee:

Carl Anderson <ccc>

Status:

RESOLVED FIXED

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

major

Priority:

Flags:

cbridgha: review+

Version:

1.5.5

Target Milestone:

3.0.5 P

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

343558

Bug Blocks:

348221, 348396

Attachments:

Description	Flags
Keep the current Methods "valid"	none

Description Carl Anderson

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

2011-04-21 11:03:21 EDT

Created attachment 193844 [details]
Keep the current Methods "valid"

Comment 2 Chuck Bridgham

2011-04-22 15:27:57 EDT

approved

Comment 3 Carl Anderson

2011-04-22 17:17:38 EDT

Committed to R3_0_5_patches