I think our messages crossed each other on the wire... ;-) -> richard
BJ Hargrave wrote: > Ask Richard Hall :-) I am sure he can provide some use cases. > > BJ Hargrave > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the OSGi Alliance > [EMAIL PROTECTED] > Office: +1 407 849 9117 Mobile: +1 386 848 3788 > > > > "Kevin Riff" <[EMAIL PROTECTED]> > Sent by: [EMAIL PROTECTED] > 09/05/2006 04:14 PM > Please respond to > OSGi Developer Mail List <[EMAIL PROTECTED]> > > > To > "OSGi Developer Mail List" <[EMAIL PROTECTED]> > cc > > Subject > Re: [osgi-dev] Inserting Properties at runtime > > > > > > > I’m curious, Tom. What is the use case for running multiple frameworks in > the same VM? > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Watson > Sent: September 5, 2006 3:59 PM > To: OSGi Developer Mail List > Subject: Re: [osgi-dev] Inserting Properties at runtime > > > This will lead to issues when you run in an environment where there is > more than one OSGi framework running in the VM at the same time. In this > environment some framework implementations will have instance specific > properties for BundleContext properties. I know Equinox does this when > running multiple frameworks in the same VM and I think Felix does the same > thing. > > In this case you may not see the system property changes in the > BundleContext properties because they only represent the properties for > the specific instance of the framework while the System properties > represent global properties for the whole VM environment. If you can live > with the property being global to the whole VM then you should get the > property using the System.getProperty instead of > BundleContext.getProperty. > > Another option would be to request OSGi add a BundleContext.setProperty > method. This way we can set the instance specific framework properties in > the case where multiple Frameworks are running in the same VM. > > Tom > > > > Andrew Eberbach/Durham/[EMAIL PROTECTED] > Sent by: [EMAIL PROTECTED] > 09/05/2006 02:17 PM > > > Please respond to > OSGi Developer Mail List <[EMAIL PROTECTED]> > > > > To > OSGi Developer Mail List <[EMAIL PROTECTED]> > cc > > Subject > Re: [osgi-dev] Inserting Properties at runtime > > > > > > > > > > > Well, I managed to find the answer myself. I didn't realize that even > after startup you can do a System.setProperty() and the Context will pick > it up. I'm not sure if this is 100% pure, but it works in my environment > (equinox) so that's all I need. > > Thanks, > Andrew > > Andrew Eberbach > Autonomic Computing > (919) 254-2645 > T/L: 444-2645 > [EMAIL PROTECTED] > > Andrew Eberbach/Durham/[EMAIL PROTECTED] > Sent by: [EMAIL PROTECTED] > 09/05/2006 02:21 PM > > > Please respond to > OSGi Developer Mail List <[EMAIL PROTECTED]> > > > > To > [EMAIL PROTECTED] > cc > > Subject > [osgi-dev] Inserting Properties at runtime > > > > > > > > > > > > Hi, > > Is it possible to set a property without using ConfigurationAdmin? What > I'm trying to do is insert one property during my bundle's startup so that > other bundles can see it. > > Thanks, > Andrew > > Andrew Eberbach > Autonomic Computing > (919) 254-2645 > T/L: 444-2645 > [EMAIL PROTECTED] > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > > > _______________________________________________ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
