Section 3.10.2 (Manifest Localization) of the R4 specification states
that
All headers in a bundle's manifest can be localized. However, the
Framework must always use the non-localized versions of headers that
have Framework semantics.
I can make a guess as to which of the 23 manifest
If you are going to be packaging open source libraries as OSGi
bundles, please be very careful about versioning.
The semantics of versioned dependencies (e.g. in Require-Bundle
constraints) in OSGi imply specific compatibility requirements.
Open source is open source, and some libraries may
The list will change over time (as we make new spec releases) and,
invariably, the spec team will screw up and and the list will be
incorrect. :-) So we chose to not put such a list in the spec.
For each header defined by the spec, if the framework will use the header
value in some way (e.g.
BJ,
I chuckled at your reply. The technical details are pretty much what
I thought. However, given the real subtleties of, say, bundle class
loading, I was surprised at the reluctance to enumerate headers with
framework semantics.
I have no such fears because I have a healthy experience
[EMAIL PROTECTED] wrote on 11/13/2006 12:51:48 PM:
BJ,
I chuckled at your reply. The technical details are pretty much what
I thought. However, given the real subtleties of, say, bundle class
loading, I was surprised at the reluctance to enumerate headers with
framework semantics.
