Bug 303070

Summary:

random build/compile error due to out of sync deployment descriptor

Product:

[WebTools] WTP Java EE Tools

Reporter:

Carl Anderson <ccc>

Component:

jst.j2ee

Assignee:

Carl Anderson <ccc>

Status:

RESOLVED FIXED

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

normal

Priority:

Flags:

cbridgha: review+

Version:

3.0.5

Target Milestone:

3.0.5 P

Hardware:

OS:

Windows XP

Whiteboard:

Bug Depends on:

Bug Blocks:

303635, 311448, 313608

Attachments:

Description	Flags
When the translator goes to load the file, check ONCE to make sure it is in sync	none
Same as previous, but with check for dir tree immutability	none

Description Carl Anderson

2010-02-17 10:40:58 EST

An adopter product is seeing a condition where the deployment descriptor of an EAR is out of sync with the file system.  This results in a partial load of the EAR's deployment descriptor:
1) The deployment descriptor node does not appear in Project Explorer
2) In the Java EE Module Dependencies, only one of many modules that should be selected are selected
3) The ClasspathContainer is thus flawed, with many compilation errors due to the fact that classes in modules that should be included in the classpath via the EAR Libraries are not, due to #2

Comment 1 Carl Anderson

2010-02-17 10:43:23 EST

Created attachment 159322 [details]
When the translator goes to load the file, check *ONCE* to make sure it is in sync

Comment 2 Carl Anderson

2010-02-17 12:12:15 EST

Created attachment 159343 [details]
Same as previous, but with check for dir tree immutability

To make this even safer, we need to check the workspace dir tree.  If it is already an active delta tree, leave it alone.  Otherwise, we need to create a new delta tree.

The adopter scenario occurs during startup, where an active delta tree would be most unlikely.  However, it could very well be that this same scenario could be hit well after the workspace is brought up, and possibly during an active change.  Therefore, the additional check is a good thing.

Comment 3 Chuck Bridgham

2010-02-18 00:11:09 EST

approved

Comment 4 Carl Anderson

2010-02-18 00:13:00 EST

Committed to R3_0_5_patches