felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-78) Modify framework to export proper JRE packages for the execution environment
Date Fri, 09 Jun 2006 08:03:30 GMT
    [ http://issues.apache.org/jira/browse/FELIX-78?page=comments#action_12415501 ] 

Richard S. Hall commented on FELIX-78:

If you recall, the exporting of OSGi packages was previously hard-coded in the system bundle
source, but we moved that to the config file when we implemented boot class path delegation
because we thought it would be more consistent to have all system bundle exports listed in
the config file.

I still believe this is true, so I don't want to revert. If we agree that they should be in
the config file, then there is pretty much no way to guarantee that they will always be exported,
since the user is free to edit the config file any way she sees fit. However, the default
shipping configuration of Felix will definitely properly export them in the config file. 

> Modify framework to export proper JRE packages for the execution environment
> ----------------------------------------------------------------------------
>          Key: FELIX-78
>          URL: http://issues.apache.org/jira/browse/FELIX-78
>      Project: Felix
>         Type: Improvement

>   Components: Framework
>     Reporter: Richard S. Hall
>     Priority: Minor

> The OSGi specification requires that class path classes are hidden from bundles. To expose
classes on the class path, the system bundle can be made to "export" them by adding the packages
to the org.osgi.framework.system.packages property in the config.properties file.
> The should create proper value definitions for this property for JDKs 1.3, 1.4, and 1.5
and perhaps define some way in the config.properties file to specify system property guards
for enabling/disabling various properties, so that we can add all three values to the config.properties
file, but only enable the value corresponding to the appropriate execution platform at run
> Of course, this is just one possible suggestion for a solution. Perhaps there is a better

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message