The execution environment specification simply specifies what's
included in the EEs. A JRE may or may not meet these definitions. The
framework only checks to see if a bundle's required EE is met. The
framework doesn't do any verification that the underlying JRE meets the
EE...although, it technically could, I guess, but this is not spec
mandated behavior and I am not aware that any framework impls do this.
-> richard
On 8/25/10 5:43, [email protected] wrote:
Yes, that is when the bundle manifest contains the manifest entry
"Bundle-RequiredExecutionEnvironment".
If I understood it correctly, OSGi compendium "Execution Environment"
Specification is just a listing of java packages and methods available
for a specified execution environment.
There is section in Execution Environment spec which has the following
text:
-------------
The information is included here for completeness. However, it is likely
that
tools will be developed by vendors that validate the compliance of
Service
Platforms and bundles in relation to an Execution Environment. For that
reason, it is possible to download a JAR file containing all the
signatures as
Java class files from the OSGi web site, see [2] Downloadable Execution
Environments.
-------------
Here again I believe the framework will have some way of finding what
execution environment it running on. When a bundle is installed based on
the bundle manifest entry " Bundle-RequiredExecutionEnvironment" it will
check if the bundles is only using methods listed for that execution
environment (as per module spec, given below).
------------
If a bundle includes this header in the manifest then the bundle must
only
use methods with signatures that are contained within a proper subset of
all
mentioned execution environments. Bundles should list all (known)
execution
environments on which it can run the bundle.
A bundle can only resolve if the framework is running on a VM which
implements one of the listed required execution environments. Frameworks
should recognize that the current VM can implement multiple execution
environments. For example, Java 6 is backward compatible with Java
5 and a bundle requiring the Java 6 execution environment must resolve
on
a Java 6 VM. The Bundle-RequiredExecutionEnvironment header can not
hinder a bundle from being successfully installed.
--------------
Framework will have to do this check based on the package/method list
specified for each execution environment. Is that correct?
In that case, Can we say that framework will be implementing the logic
which checks the compliance of service platform& (any installed) bundle
with the Execution Environment spec?
Thanks,
Prakash
-----Original Message-----
From: Richard S. Hall [mailto:[email protected]]
Sent: Tuesday, August 24, 2010 9:49 PM
To: [email protected]
Subject: Re: Compendium services implemented by Felix
On 8/24/10 11:50, [email protected] wrote:
One more question.
Does Felix implement Compendium Execution Environment Specification ?
The Felix framework will verify execution environment requirements of
bundles.
-> richard
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, August 24, 2010 8:38 PM
To: [email protected]
Subject: RE: Compendium services implemented by Felix
Thank you all for the replies.
This the only link on the web which talks about OSGi service
implementation status of various OSGi projects. Looks like it is the
updated list.
http://en.wikipedia.org/wiki/OSGi_Specification_Implementations
-----Original Message-----
From: Rodrigo Madera [mailto:[email protected]]
Sent: Tuesday, August 24, 2010 8:04 PM
To: [email protected]
Subject: Re: Compendium services implemented by Felix
I even entertained the thought of writing a book that
simply categorizes and briefly introduces the various Apache projects
to
better inform the community where to find what they need...
I would buy two copies... instantly.
;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
