In general, it is cool to be able to auto-generate the available
packages. However, I don't see it being a good idea in practice.
The package list should generally be a rather static set, so I don't see
people wanting to re-generate this each time they start their framework
for a given deployment. A better way to use this capability would be to
use it to generate your static system packages property for your
config.properties file when you deploy the framework.
Just my $0.02...
-> richard
Karl Pauls wrote:
In addition to the predefined package list solution we have now, I've
implemented an auto-detect solution. I think we could integrate the
two approaches by allowing a special property (e.g.,
${auto.detect.packages}) too. What it does is to scan the available
packages at system start-up.
Due to richard probably complaining about this being what we had in
the first place (namely, all packages are available) I've included the
possibility of a filter as well i.e., it is possible to filter the
packages by means of an LDAP filter based on two properties:
Package-Name and Package-Source. For Example:
${auto.detect.packages}
package.filter=(|(Package-Name=java.*)(Package-Name=javax.*)(Package-Name=org.omg.*))
yields the same result as our static defined package-lists.
Additionally, one would be able to add special stuff either by name or
by location:
package.filter=(|(Package-Name=java.*)(Packag-Name=quicktime.*)(Package-Source=classes))
Does this sound like a good idea?
regards,
Karl
On 6/9/06, Richard S. Hall (JIRA) <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/FELIX-78?page=all ]
Richard S. Hall closed FELIX-78:
--------------------------------
Resolution: Fixed
Excellent. We should keep this command around for JDK 1.6...thanks
Niclas. I have committed the new config file with update property
definitions.
> 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
> Attachments: jre1.3.packages, jre1.3.packages, jre1.4.packages,
jre1.4.packages, jre1.5.packages, jre1.5.packages
>
> 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 time.
> Of course, this is just one possible suggestion for a solution.
Perhaps there is a better one.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
