Bugzilla – Full Text Bug Listing
| Summary: | Provide api for determining web context root providing related ear project | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Chuck Bridgham <cbridgha> |
| Component: | jst.j2ee | Assignee: | Chuck Bridgham <cbridgha> |
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ccc, neil.hauge, raghunathan.srinivasan |
| Version: | 3.3.1 | Flags: | cbridgha:
pmc_approved?
(david_williams) raghunathan.srinivasan: pmc_approved+ cbridgha: pmc_approved? (naci.dai) cbridgha: pmc_approved? (deboer) neil.hauge: pmc_approved+ cbridgha: pmc_approved? (kaloyan) cbridgha: pmc_approved? (cbridgha) |
| Target Milestone: | 3.3.2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | PMC | ||
| Bug Depends on: | 353941 | ||
| Bug Blocks: | |||
|
Description
Chuck Bridgham
I realized this api was never put in 3.3.2 or HEAD stream.... We can use the same patch from other stream https://bugs.eclipse.org/bugs/attachment.cgi?id=202929&action=diff It is adding api so I'll add PMC flags... Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. new API - so flagging for PMC approval Is there a work-around? If so, why do you believe the work-around is insufficient? This is a utility api How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Yes Junit added Give a brief technical overview. Who has reviewed this fix? Carl Anderson has reviewed the code. This utility simply checks if the WAR is contained inside the Ear passed, if not, it will return the setting from the web component file, if contained, it will return the context root specified in the Ear DD xml file. What is the risk associated with this fix? None Assuming you have reviewed and approved! Committed to both 3.3 and HEAD streams |