| Summary: | Creating Connector 1.6 project with DD generates two <diplay-name> tags, one of the empty. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Hari Shankar <hshanka> | ||||
| Component: | jst.j2ee | Assignee: | Hari Shankar <hshanka> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ccc, jsholl, neil.hauge | ||||
| Version: | unspecified | Flags: | hshanka:
pmc_approved?
(david_williams) hshanka: pmc_approved? (raghunathan.srinivasan) hshanka: pmc_approved? (naci.dai) hshanka: pmc_approved? (deboer) neil.hauge: pmc_approved+ hshanka: pmc_approved? (kaloyan) cbridgha: review+ |
||||
| Target Milestone: | 3.2 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Hari Shankar
Created attachment 167633 [details]
patch
This patch removes the display name tag from the template file, since it is being added with the correct value in the install delegate.
approved * 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.
The issue here is that an unwanted/invalid xml content is generated. This causes display issues in the navigator model node.
* Is there a work-around? If so, why do you believe the work-around is insufficient?
Workaround is to manually edit the deployment descriptor to remove the additional display-name tag. This may not be a good interim solution because it requires the users to edit the xml and fix issues in the tooling generated contents.
* How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?
Tested creating a connector project with DD on windows and ensured that only one display-name tag is added.
* Give a brief technical overview. Who has reviewed this fix?
This fix has been reviewed by Chuck Bridgham.
* What is the risk associated with this fix?
There are no known risks associated with the fix.
code checked into head for WTP 3.2 RC1 |