Community
Participate
Working Groups
Build Identifier: 3.0.5 P This bug is related to bug 322173. In bug 322173, a new method has been added to find out the affected project. However, there is currently no way for the adopter to figure out if all the deployer has implemented the new method. This will make the adopter not be able to decide whether to use the information on the new methods or not. This information is essential to support properly the case where some deployer has not provided the affect project information to avoid regression on those scenarios. This bug is to address this issue by introducing a new method to tell the adoptor on whether all deployers has provided the affected project information. Reproducible: Always
Created attachment 176846 [details] v1.0 This patch adds a method isAllDeployersProvideAffectedProjects() to the J2EEDeployOperation for adopter to find out if all deployers have provided the affect projects information.
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 on bug 322173 on the original problem. This bug is required to ensure adopter has a way to provide backward compatibility in case some deployer does not implement the new extension provided on 322173. Without this bug fix, the adopter won't be able to make use of bug 322173 without introducing potential functional regression.
A hotbug_request is not required in this case. I am marking this as major due to the possible regressions that could be introduced without this change.
approved
Committed to R3_0_5_patches
