implementing the framework, any header whose value you
> would need
> to use should be the original, unlocalized value.
>
> BJ Hargrave
> Senior Technical Staff Member, IBM
> OSGi Fellow and CTO of the OSGi Alliance
> [EMAIL PROTECTED]
>
> office: +1 407 849 9117
> mo
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 h
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 he
I support the addition of new operations to the filter syntax.
I do *not* support the capability of user-supplied filter extensions.
In general: address the real shortcomings, but keep it simple.
/djk
> Message: 1
> Date: Thu, 2 Nov 2006 11:59:32 +0100
> From: Peter Kriens <[EMAIL PROTECTED]>
(sound of David smacking his own forehead)
Of course. Sorry for the waste of bandwidth. Thanks, Tom (and BJ ;-)
/djk
> David,
>
> I moved this post to the equinox newsgroup at
> news://news.eclipse.org/eclipse.technology.equinox under the thread
> "using
> ecore in an equinox runtime".
>
> T
I'm trying to use ecore in an Equinox OSGi environment. I'll try
first to state the problem and the symptoms without going deep into
details, and provide any additional info in any follow-ups.
I am installing a fairly large set of required bundles...about a
hundred. This is the result of a
Responses in-line.
> Date: Wed, 29 Mar 2006 09:18:20 +0200
> From: Peter Kriens <[EMAIL PROTECTED]>
> Subject: Re: [osgi-dev] Indirect dependencies in OSGi/Equinox
> To: David Kemper <[EMAIL PROTECTED]>
> Cc: osgi-dev@bundles.osgi.org
> Message-ID: <[EMAIL PROTE
Thanks for the many replies so far. At the risk of confusing the
issue, let me give more details about my use case.
I would like to leverage the OSGi metadata and methodologies to
componentize our overlapping runtimes. In other words, I want to
have a single bundle store with tens/hundreds
All,
I am looking for approaches and best practices for expressing
indirect dependencies including, but not limited to
- code that uses introspection (e.g. Class.forName())
- support for Service Provider Interfaces (SPIs) where multiple
providers can be supplied (e.g. cryptographic extension