[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Bundle Manifest processing and Manifest Localization

But https://bugs.eclipse.org/bugs/show_bug.cgi?id=184460 has been opened to track this issue.

This is something we will need to investigate for the next release.  It is too late in the 3.3 release to make such a subtle change.  There is no way of knowing all the clients which depend on this behavior.  I know the framework definitely depends on the values being trimmed.  It is very likely PDE also depends on this behavior.


Danail Nachev <d_nachev@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

05/10/2007 07:26 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
[equinox-dev] Bundle Manifest processing and Manifest Localization


Currently manifest parser trims all manifest headers' values on load. In
most cases this doesn't make difference, because whitespaces are ignored
in all of the headers which have a meaning in OSGi. However, there is a
case, where the whitespace should make a difference.
This is the case of localized manifest headers. In this case the value
can contain spaces both in the beginning and in the end.
This is supported by the OSGi specification $3.10.2 Manifest Localization.

Another thing which I spotted was that the header name is trimmed too. I
didn't have time to examine what problems arise from that, but this is a
violation of the Jar manifest spec.

I wonder, first, do you plan to address these concerns? And second, is
there something particularly, which requires that the header name and
value are trimmed?

Danail Nachev . Software Engineer/Development Tools
ProSyst Labs EOOD
1606 Sofia, Bulgaria . 48 Vladajska Str.
Phone:  +359 (0)2 952 35 81/102 . Fax +359 (0)2 953 26 17
http://www.prosyst.com . d_nachev@xxxxxxxxxx
stay in touch with your product.

equinox-dev mailing list