Seems to me you should file a bug against equinox. The spec is authoritative and the RI is used to illuminate the dark corners of the spec.
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
[EMAIL PROTECTED]
Office: +1 386 848 1781 Mobile: +1 386 848 3788
----- Original Message -----
From: David Kemper [EMAIL PROTECTED]
Sent: 01/19/2008 07:17 PM
To: [email protected]
Subject: [osgi-dev] Bundle-NativeCode and case
I see from the specification (OSGi R4.1) Section 4.4.3 Environment
Properties that the values of both org.osgi.framework.processor and
org.osgi.framework.os.name "...should be matched case insensitive".
However, it appears that the Equinox implementation does not do case-
insensitive comparisons when evaluating native code constraints.
For example, the example given in 3.9 Loading Native Code Libraries
gives one example clause
...
lib/solaris/libhttp.so ;
osname = Solaris ;
osname = SunOS ;
processor = sparc,
...
This fails on Equinox (tested using some simple code build on the
Equinox Resolver) because the processor alias is the capitalized
"Sparc".
Is this a bug, or is the spec broader than it should be?
I raise this question here because it is my impression that Equinox is
the OSGi reference implementation.
/djk
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
