Community
Participate
Working Groups
Current members() api uses flexible project api to aggregate all folder/file content, which can be very slow with large workspaces. members() method may have optimization that should be investigated, but recognizing the Module is already in an optimized state, and populating the IModule files by traversing a single root will greatly improve performance.
*** Bug 158622 has been marked as a duplicate of this bug. ***
*** Bug 159035 has been marked as a duplicate of this bug. ***
Created attachment 51581 [details] Proposed Patch
Created attachment 51643 [details] Proposed patch Updated patch with comments from Chuck about only caring about non manifest references in web projects in the check for optimized structure. We should never be concerned with manifest references because they are not packaged in the current component.
The J2EEFlexProjDeployable, which handles J2EE publish deploying, needs to be smarter. If it detects that it is in an optimized structure, generally, meaning one content root and one output folder, that are also the same folder, then instead of having to go through expensive virtual API, we can just pass the root folder contents to the server deploy tools. This will considerably improve time to publish and deploy on the server, especially in larger workspaces. The patch is attached and has good documentaion embedded explaining the changes.
approve
+1
This is released to the 2.0 and 1.5.2 streams for the 101106 builds based on PMC feedback from David Williams.
+1 for WTP 1.5.2. Why are you releasing with just one vote? You need to allow adequate time for PMC review.
+1 for 1.5.2
verified
Closing.
