Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332167 - generic capability attribute lists should not be trimmed.
Summary: generic capability attribute lists should not be trimmed.
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.7 M5   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-08 15:13 EST by Thomas Watson CLA
Modified: 2010-12-09 13:27 EST (History)
0 users

See Also:

Attachments
patch (1.87 KB, patch)
2010-12-08 15:15 EST, Thomas Watson 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 Thomas Watson CLA 2010-12-08 15:13:30 EST 
When specifying a Provide-Capability header an attribute may specify a list of String values:

Provide-Capability: foo; s.attr:List<String>="aString,bString,cString"

When the attribute is of type String then whitespace is significant.  Currently the parser is trimming the whitespace from the beginning and end of the overall attribute value.  This makes the following the same as the above header, which is not correct:

Provide-Capability: foo; s.attr:List<String>=" aString,bString,cString "
Comment 1 Thomas Watson CLA 2010-12-08 15:15:47 EST 
Created attachment 184815 [details]
patch
Comment 2 Thomas Watson CLA 2010-12-09 13:27:52 EST 
Patch released to head.