[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[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.