Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332160 - Manifest entries with backslash are not handled correctly by manifest page in deployment assembly page
Summary: Manifest entries with backslash are not handled correctly by manifest page in...
Status: RESOLVED FIXED
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.common (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Aidyl Kareh CLA
QA Contact: Carl Anderson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-08 13:13 EST by Aidyl Kareh CLA
Modified: 2010-12-09 12:05 EST (History)
2 users (show)

See Also:
ccc: review+
jsholl: review+

Attachments
Proposed Patch (4.61 KB, patch)
2010-12-08 13:21 EST, Aidyl Kareh CLA 		no flags 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 Aidyl Kareh CLA 2010-12-08 13:13:41 EST 
Build Identifier: WTP 3.2.3

In the 'Manifest Entries' tab of the 'Deployment Assembly' properties page, entries that have a backslash are not displayed in the table (e.g. 'ejbJars\EjbTest.jar'). The table in the 'Manifest Entries' tab should show all the entries in the MANIFEST.MF file.

Reproducible: Always
Comment 1 Aidyl Kareh CLA 2010-12-08 13:21:32 EST 
Created attachment 184803 [details]
Proposed Patch

The problem is caused because manifest entries are broken down to IVirtualReference objects and the backslash gets lost in the process (breaks the entry down to runtime path and archive name). This patch updates the code so that if a backslash is found, then the archive name is set to the whole manifest entry and the runtime path is set to an empty value.
Comment 2 Jason Sholl CLA 2010-12-09 12:05:09 EST 
Code checked into 32M and HEAD for WTP 3.2.3 and 3.3