Bug 322173 - J2EEDeployOperation does not allow callers to get a list of affected projects
Summary: J2EEDeployOperation does not allow callers to get a list of affected projects
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.0.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 3.0.5 P   Edit
Assignee: Jason Peterson CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-09 14:16 EDT by Troy Bishop CLA
Modified: 2010-08-13 18:03 EDT (History)
2 users (show)

See Also:
cbridgha: review+

Attachments
possible patch (4.29 KB, patch)
2010-08-09 14:17 EDT, Troy Bishop CLA 		ccc: iplog+
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 Troy Bishop CLA 2010-08-09 14:16:41 EDT 
Build Identifier: 

The current implementation of J2EEDeployOperation does not allow the caller of this operation to retrieve a set of IProjects that were modified by any deployers that were executed.  In a product that adopts WTP having this support would allow us to overcome a rather painful publishing performance problem that occurs with our server adaptor (it executes this J2EEDeployOperation as a publishing task).

Attached is a possible patch which adds this API to J2EEDeployOperation and should not introduce any compatibility concerns with anyone that implements the current ICommand interface.

Reproducible: Always
Comment 1 Troy Bishop CLA 2010-08-09 14:17:33 EDT 
Created attachment 176174 [details]
possible patch
Comment 2 Jason Peterson CLA 2010-08-10 09:48:06 EDT 
Hey Chuck,  

Can you review the patch?
Comment 3 Troy Bishop CLA 2010-08-10 14:11:29 EDT 
Hot bug request to ask that this be included in 3.0.5_patches as well:

1.  Affiliation

IBM

2. Be clear on which release you want this bug to be fixed in, or "last workable" date, if requesting a patch.

3.0.5_patches

3. Justify why this is a hotbug. Note that "our users don't like the bug" is not the type of reason that gets much attention. The motivation we are looking for to justify a P1-like priority is, basically, "this bug blocks our adoption of WTP" (explaining why, of course).

See comment 0 of this report and the description in bug id=322261.
Comment 4 Chuck Bridgham CLA 2010-08-10 16:02:40 EDT 
approved - thanks for preserving existing api
Comment 5 Carl Anderson CLA 2010-08-13 17:28:21 EDT 
Commited to R3_0_5_patches