[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864313#action_12864313 ] Richard S. Hall commented on FELIX-2324: But it also says org.osgi.framework.executionenvironment is a comma-separated list of all EEs implemented by the framework, so I do think it should be multi-valued too. Bundles wouldn't be able to list future EEs, so it is up to the framework to indicate backwards compatibility of EEs, I would think. I agree with Christopher that we should set the value to be all SE EEs up until the detected SE EE. However, I am not too worried about whether or not setting the property overrides the value since it's value is not too difficult to recreate. > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864167#action_12864167 ] Guillaume Nodet commented on FELIX-2324: Are you sure multiple values need to be supported on the framework level rather than the bundle requesting it ? Section 3.3.1 of the OSGi Core spec 4.2 says the bundle should list all environements it can run on. So I think the framework only needs to set a single value. In addition, the values have been standardized. > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864139#action_12864139 ] Christopher Blunck commented on FELIX-2324: --- I looked up standardization on execution environments in JVMs and I didn't get very far. It appears that "execution environments" is more of a concept than an actual underlying artifact (accessible via a property or some other construct). There appears to be some disagreement between Bundle-RequireExecutionEnvironment values where some people cite "1.3" vs "J2SE-1.3": http://www.mail-archive.com/d...@slf4j.org/msg00843.html This smells like a very slipper slope from a framework perspective. imo the framework should detect the current JVM version and then step backwards in minor versions in an additive fashion, appending each value to the "execution environments" that are supported. For example... If JVM 1.6.0_X is detected then the execution environments that should be supported are: J2SE-1.6, J2SE-1.5, J2SE-1.4, J2SE-1.3, J2SE-1.2, J2SE-1.1, J2SE-1.0. If an application developer specifies "-Dorg.osgi.framework.executionenvironment=foo" I'm on fence as to what happens. In one hand I respect the application developer's perspective that "foo" is the ONLY ee that their app suports. OTOH I also appreciate the perspective that "foo" should be additive to the other sensed environments. Perhaps a second system property is needed here? Or ... ? > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863884#action_12863884 ] Richard S. Hall commented on FELIX-2324: ok. Well, all I am thinking about doing is adding some property substitution magic in the default.properties file that ships with the framework so that it tries to select a default value based on the JRE. This shouldn't be problematic, since anyone will be able to override it by specifying the property explicitly in the framework configuration properties. Just like we do currently for system packages. > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863878#action_12863878 ] Christopher Blunck commented on FELIX-2324: --- I don't know as I'm pretty new to Karaf. It strikes me though that ee is a framework concept and not a Karaf concept. I also know that pax-runner has some ee related functionality within it. Might be worth considering how that functionality works and if it can be incorporated into the Felix framework. > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2324) Support execution environment so that OBR works properly
[ https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863875#action_12863875 ] Richard S. Hall commented on FELIX-2324: I was thinking about adding this in the default properties for the framework, not in Karaf. Are there actually two issues here: one for the framework and one for Karaf? > Support execution environment so that OBR works properly > > > Key: FELIX-2324 > URL: https://issues.apache.org/jira/browse/FELIX-2324 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-2.0.5 >Reporter: Christopher Blunck >Priority: Minor > Fix For: framework-3.0.0 > > > Basic use case here is that I'd like to use Jackson within OBR. Jackson > expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility > for supported execution environments. > I can set: > JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5" > before I start karaf from the command line but this seems like a hack. It's > very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM. > Ideally at startup time Karaf could look at the runtime and determine the JVM > version (at the very least). It could then expose the execution environment > somehow (presumably in a way that OBR would understand). > We should still be able to explicitly set the > org.osgi.framework.executionenvironment system property but ideally it'd be > additive to the ee's that Karaf senses when it starts up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
