search

ops4j / org.ops4j.pax.runner

Multi Framework OSGi Runner
http://team.ops4j.org/wiki/display/paxrunner/
47 stars 39 forks source link

Felix does not set System properties out of framework properties [PAXRUNNER-229] #260

Open ops4j-issues opened 15 years ago

ops4j-issues commented 15 years ago

Alin Dreghiciu created PAXRUNNER-229

Divers pax runner scanners allows setting of framework properties. This properties are sent to frameworks via their specific configuration file and can be accessed via bundle context.
Even if not required by specs it seems like Equinox is setting the framework properties as System properties. At least it does for initial system properties from the configuration files, but could be the case that the properties are also synchronized during the lifetime of the framework. This is useful for bundles or apps which are not using the bundle context but system properties for accessing properties.

But this is not the case for Felix. Felix will not set the System properties so apps like above will fail or not use them.
E.g. Spring and spring dm using placeholders (PropertyPlaceholderConfigurer ) will fail if the values are not configured and the last resort is System properties

To avoid such situation it will be a good improvement that framework properties will be set also as system properties (-D) while launching Felix.

Fixed in: 0.18.0 Votes: 0, Watches: 1

Referenced issues

is related from:

ops4j-issues commented 15 years ago

Alin Dreghiciu commented

Released as part of 0.18.0

ops4j-issues commented 11 years ago

Tuomas Kiviaho commented

It seems that that changes in Pax Scanner were not released simultaneously and hence pom.xml of Pax Runner still refers to old Pax Scanner.