The compiler attempts to compile your bundle against the JRE associated with the EE you choose.OSGi allows bundles to be marked with the minimum execution environment they require (see the Setting the Execution Environment). This results in a 40-50MB disk/transfer footprint savings over J2SE-1.5 JREs! Second, an application written entirely of bundles such as A can ship on a Foundation 1.0 JRE. First, A can be used in embedded devices where Foundation 1.0 is quite popular. The execution environment needed by your bundle is key in both situations.Ĭonsider the different outcomes for some bundle A that requires just Foundation 1.0 and a bundle B that requires J2SE-1.5. This allows them to be used in a wider range of situations and results in a smaller overall footprint for applications built of these bundles. So what does this mean to me and my bundles?
The system can then be configured to use a specific JRE to implement that execution environment.Įxecution environments are relevant both to development (compile) time and runtime. For example, rather than talking about a specific JRE, with a specific name at a specific location on your disk, you can talk about the J2SE-1.4 execution environment. 10 Installing Execution Environment DescriptionsĮxecution environments (EEs) are symbolic representations of JREs.7.2 Compiling against more than is required.5 I have prerequisites that require version X to run, so shouldn't I require version X too?.4 Which Execution Environment should I use?.2 So what does this mean to me and my bundles?.