Implementing a filter class is not that hard because the filter
language is optimized for parsing. You can always take the filter
implementations of Felix, Knopflerfish, or Equinox.
Kind regards,
Peter Kriens
AQ> On 8/20/06, BJ Hargrave <[EMAIL PROTECTED]> wrote:
AQ>
AQ> One expression b
On 8/20/06, BJ Hargrave <[EMAIL PROTECTED]> wrote:
One _expression_ but it can be a compound _expression_. For example:(&(foo=bar)(xyz>=10)(|(vendor=osgi)(vendor=acme)))
Well, the evaluation become a little less trivial :-)--
___
osgi-dev mailing list
os
On 8/20/06, BJ Hargrave <[EMAIL PROTECTED]> wrote:
It is quite possible we forgot to add it to the Contants class. Why don't you open a bug on the
bundles.osgi.org bugzilla system so we can add it inthe next release?Done.--
___
osgi-dev mailing list
osg
Message - From: osgi-dev-bounces Sent: 08/20/2006 02:15 PM To: OSGi Developer Mail List" <[EMAIL PROTECTED]> Subject: Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
Just a confirmation, please.In Bundle-NativeCode, the 'selection-filter' can contain one
obile: +1 386 848 3788 - Original Message - From: osgi-dev-bounces Sent: 08/20/2006 01:26 PM To: OSGi Developer Mail List" <[EMAIL PROTECTED]> Subject: Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
Another one, regarding framework constants for bundle he
Just a confirmation, please.In Bundle-NativeCode, the 'selection-filter' can contain one and only one _expression_ to validate, right ?--
___
osgi-dev mailing list
osgi-dev@bundles.osgi.org
http://bundles.osgi.org/mailman/listinfo/osgi-dev
ECTED]>
Sent by: [EMAIL PROTECTED]
08/20/2006 01:52 PM
Please respond to
OSGi Developer Mail List <[EMAIL PROTECTED]>
To
"OSGi Developer Mail List" <[EMAIL PROTECTED]>
cc
Subject
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
Another li
Another one, regarding framework constants for bundle header parsing.The Bundle-NativeCode is composed of native clauses.Each native clause indicates osname(s), processor(s), etc. and selection-filter(s).
But R4 Spec org.osgi.framework.Constants
does not have a constant named like BUNDLE_NATIVECOD
Another litle related question, concerning alias provided for org.osgi.framework.processor (R4, pp.90-91)Does PowerPC has one alias as 'power ppc' or two as 'power' & 'ppc'Idem for x86 : 'pentium', 'i386', 'i486', 'i586' & 'i686' are all aliases, I suppose ...
--
_
Thanks a lot to Peter & BJ.I finally understand ... and try a little sum up :1/ Parameters 'osname' & 'processor' are not mandatory. But they are required during the evaluation time of the native clause. If one of them is empty or missing, the clause will never be selected.
2/ The selection filter
Bundle-NativeCode manifest header
1) They are necessary in so far as clauses without them can not be
selected. However from a grammar point of view they are not mandatory.
2) Since they are not mandatory in the grammar, we do not need to make the
grammar more complicated :-)
Algorithm
OK. Let
AQ> Question(s)
AQ> 1/ The two parameters 'osname' and 'processor' are mandatory.
AQ> Does anybody can tell me whether it's right ?
well, they can never be selected so any clause with an osname and
processor is useless. However, we did not make them explicitly
mandatory so a header without osname/p
12 matches
Mail list logo
