This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 205310 - Preferences API running within the IDE cannot access values set outside the IDE on Windows 7 x64
Summary: Preferences API running within the IDE cannot access values set outside the I...
Status: RESOLVED INCOMPLETE
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 7.0.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 20:23 UTC by jallbery
Modified: 2012-01-16 19:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jallbery 2011-11-18 20:23:43 UTC
The method Preferences.systemNodeForPackage fails even though the node and values were already set by an application running outside the IDE.   This appears to be because the 64-bit JVM running outside Netbeans IDE uses the registry node

HKEY_LOCAL_MACHINE\Software\Javasoft\Prefs\

while the 32-bit JVM running within Netbeans IDE uses the node

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Javasoft\Prefs\

(I believe this is a side effect of "Registry virtualization" when running 32-bit apps under 64-bit Win7.)

You can work around this issue in a development environment by running the Netbeans IDE with Administrator privileges and then running the application to create the system node and its entries from within the IDE.   You can then exit the IDE, and then restart it (without administrator privs).  Subsequent applications run within the IDE will be able to access the values set by the program that was run from within IDE while it was running as Administrator.  However, changes made to the system preferences values from outside the IDE will not be seen from within the IDE.
Comment 1 Dusan Balek 2011-11-22 13:19:29 UTC
Unfortunately, I don't see any relation to the NetBeans internal javac compiler.
Comment 2 jallbery 2012-01-08 04:36:51 UTC
(In reply to comment #1)
> Unfortunately, I don't see any relation to the NetBeans internal javac
> compiler.

Well, then, where do you suggest I post this?
Comment 3 Jan Lahoda 2012-01-16 19:26:20 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > Unfortunately, I don't see any relation to the NetBeans internal javac
> > compiler.
> 
> Well, then, where do you suggest I post this?

Hm, at least to me, the problem and its relation to NetBeans is not clear at all. Sounds that it may be related to the JDK/JRE, but as I do not understand the problem, it is hard to say anything.

Please describe what you are trying to do, how do you do it, what do you expect, and what are the actual results. Thanks.