Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319679 - BundleContext.getProperty does not find all system properties
Summary: BundleContext.getProperty does not find all system properties
Status: RESOLVED DUPLICATE of bug 490890
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 320459 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-07-13 06:45 EDT by Glyn Normington CLA
Modified: 2019-10-22 09:25 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2010-07-13 06:45:33 EDT 
I noticed the following behaviour in a test which sets a system property (using System.setProperty) after Equinox is launched. BundleContext.getProperty returns null for the property while System.getProperty correctly returns the property.

According to the javadoc of BundleContext.getProperty:

    "If the key is not found in the Framework properties, the system properties are then searched."

The implementation of BundleContext.getProperty delegates to Framework.getProperty which looks up the property in a "properties" instance member. This instance member is set up when the framework is initialised and does not seem to take into account system properties which are set after the framework is initialised.
Comment 1 Thomas Watson CLA 2010-07-21 09:18:31 EDT 
*** Bug 320459 has been marked as a duplicate of this bug. ***
Comment 2 Sahoo CLA 2010-10-24 22:42:07 EDT 
When can we expect this issue to be fixed?
Comment 3 Eclipse Genie CLA 2019-10-22 06:43:23 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Thomas Watson CLA 2019-10-22 09:25:26 EDT 
This was fixed by bug 490890.

*** This bug has been marked as a duplicate of bug 490890 ***