Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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 but it can be a compound expression. For example: (&(foo=bar)(xyz>>=10)(|(vendor=osgi)(vendor=acme))) AQ> AQ> Well, the evaluation become a little less trivial :-) -- Peter Kriens Tel +33467542167 9C, Avenue St. DrézéryAOL,Yahoo: pkriens 34160 Beaulieu, FranceICQ 255570717 Skype pkriens Fax +1 8153772599 ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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 osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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 osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
One _expression_ but it can be a compound _expression_. For example:(&(foo=bar)(xyz>=10)(|(vendor=osgi)(vendor=acme)))BJ HargraveSenior Technical Staff Member, IBMOSGi Fellow and CTO of the OSGi Alliance[EMAIL PROTECTED]Office: +1 407 849 9117 Mobile: +1 386 848 3788 - Original 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 and only one _expression_ to validate, right ?-- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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 in the next release?BJ HargraveSenior Technical Staff Member, IBMOSGi Fellow and CTO of the OSGi Alliance[EMAIL PROTECTED]Office: +1 407 849 9117 Mobile: +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 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_NATIVECODE_XXX corresponding to this 'selection-filter' section.Is this a error or is my reflexion wrong ?-- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
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 and only one _expression_ to validate, right ?-- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
Each word is an alias. So powerpc has power and ppc as aliases. Same for x86. Each is an alias. BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 407 849 9117 Mobile: +1 386 848 3788 "Arnaud Quiblier" <[EMAIL PROTECTED]> 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 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 ... -- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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_NATIVECODE_XXX corresponding to this 'selection-filter' section.Is this a error or is my reflexion wrong ?-- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]
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 ... -- ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] R4 Chapter 110 - Initial Provisioning
On Sunday 20 August 2006 19:14, Niclas Hedhman wrote: > Gang, > > I want to clarify that I understand this specification, before running off > doing stuff; Hmmm, disregard this mail entirely. I'll reformulate after pondering some more on how things are expected to be. Cheers Niclas > 1. Is it correct that Initial Provisioning is either supported directly by > the framework? My concern revolves around the PROVISIONING_START_BUNDLE > must be given AllPermissions, hence becoming a requirement on the > framework. A framework bootstrapper could know how to manipulate the > configuration files of the framework to make this happen, but it > seems 'icky'. > > 2. The Management Agent will always have the Name field in the Zip file > set to "provisioning.start.bundle", and "should/must/must not" one support > multiple entries with this name? My take is that it must not be supported, > as that name would also need to be stored in the Dictionary, which I think > must have unique keys. > > 3. The PROVISIONING_REFERENCE has a similar issue. "should/must/must not" > support multiple entries in the same Zip file? And what happens to the > Dictionary entry? Is it just containing the last reference loaded? > > 4. Finally, how come one don't see much implementations around this spec? > At least I have not been able to find any in the OSS world. > > > Cheers > Niclas > ___ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
[osgi-dev] R4 Chapter 110 - Initial Provisioning
Gang, I want to clarify that I understand this specification, before running off doing stuff; 1. Is it correct that Initial Provisioning is either supported directly by the framework? My concern revolves around the PROVISIONING_START_BUNDLE must be given AllPermissions, hence becoming a requirement on the framework. A framework bootstrapper could know how to manipulate the configuration files of the framework to make this happen, but it seems 'icky'. 2. The Management Agent will always have the Name field in the Zip file set to "provisioning.start.bundle", and "should/must/must not" one support multiple entries with this name? My take is that it must not be supported, as that name would also need to be stored in the Dictionary, which I think must have unique keys. 3. The PROVISIONING_REFERENCE has a similar issue. "should/must/must not" support multiple entries in the same Zip file? And what happens to the Dictionary entry? Is it just containing the last reference loaded? 4. Finally, how come one don't see much implementations around this spec? At least I have not been able to find any in the OSS world. Cheers Niclas ___ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
