Community
Participate
Working Groups
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
Created attachment 159322 [details] When the translator goes to load the file, check *ONCE* to make sure it is in sync
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.
approved
Committed to R3_0_5_patches
