Re: [osgi-dev] R4 Core Spec : Loading Native Code Libraries [ 3.9 ]

2006-08-20 Thread BJ Hargrave 
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 ?-- /arnaud

___
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 ]

2006-08-20 Thread BJ Hargrave 
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 ?-- /arnaud
___
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 ]

2006-08-12 Thread Peter Kriens 
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/processor should not generate
an error.

AQ 2/ If so, perhaps the mandatory aspect of those two parameters
AQ could be explicitly written  p.60 and the order of the parameter's
AQ presentation be changed to reflect this importance.
Thanks for the suggestion, we will discuss this for R5.

Kind regards,

 Peter Kriens

AQ Dear all,

AQ Here are my comments and questions concerning the chapter 3.9
AQ (pp. 59-63) of the OSGi Core Specification Release 4.


AQ *) Bundle-NativeCode manifest header syntax (p. 60)

AQ I would like to be totally sure to correctly understand the
AQ syntax of the 'nativecode' element of this header. 
AQ This element is composed of one or more 'path' element and one or more 
'parameter' element.
AQ One ore more 'parameter' implies that one at least of the
AQ architected attributes is mandatory.
AQ Reading further the section  3.9.1 (p. 62) describing the native
AQ code algorithm, the first step of the process seems to imply that
AQ 'osname' and 'processor' are both required in a native clause.
AQ Indeed, the other parameters can be not specified, but those can't.

AQ Question(s)
AQ 1/ The two parameters 'osname' and 'processor' are mandatory.
AQ Does anybody can tell me whether it's right ?
AQ 2/ If so, perhaps the mandatory aspect of those two parameters
AQ could be explicitly written  p.60 and the order of the parameter's
AQ presentation be changed to reflect this importance.


AQ *) Native Code Algorithm (p. 62)

AQ Perhaps I'm stupid. But I do NOT understand the last but one
AQ paragraph. It begins with If a selection filter .. and ends with
AQ ... optional clause is specified.. The paragraph before is
AQ absolutly clear, but this one exceeds my capacities. Plz help ! 


AQ Regards,


-- 
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