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 16219 - User-installed modules use incorrect layer for settings
Summary: User-installed modules use incorrect layer for settings
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Other Linux
: P1 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
: 16218 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-04 10:07 UTC by Svata Dedic
Modified: 2008-12-22 21:48 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

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 Svata Dedic 2001-10-04 10:07:19 UTC 
I've installed java module in the normal (multiuser) mode. Module's settings 
and service types appeared (correctly) as defined in the user layer.
However, if I changed service's property, the changed service was persiste in 
the user layer as well, not in the project layer.
This behaviour may lead to unexpected results after AutoUpdate of some modules.
All the services' objects have attribute SystemFileSystem.layer="project".
Comment 1 akemr 2001-10-05 16:29:18 UTC 
*** Issue 16218 has been marked as a duplicate of this issue. ***
Comment 2 Jesse Glick 2001-10-07 19:57:09 UTC 
Jan what controls this? I know that NbInstaller.loadLayers will in
this case insert the module layer into
ModuleLayeredFileSystem.userModuleLayer rather than
.installationModuleLayer, or at least this is what it is supposed to
do. Anyway SystemFileSystem.createWritableOn should not care, it
should return PRJ_FS in this case...right? If there is some problem in
org.netbeans.core.modules.* I can try to fix it, but I do not know
exactly what SFS is supposed to be doing in this case.
Comment 3 Jan Chalupa 2001-10-08 12:26:43 UTC 
Please note that #16218 was a P1. I think this issue needs to be 
resolved for the Beta. Upgrading to P1.
Comment 4 Jan Pokorsky 2001-10-08 12:41:13 UTC 
SFS.createWritebleOn decides between project layer and user layer in 
accordance with SFS.project attribute. Default is the user 
layer(session). If file does not contanin attribute its parent is 
checked. Once the file is located on any writable filesystem 
SFS.createWritebleOn always returns this one.

assigned back to Jesse.
Comment 5 Jesse Glick 2001-10-08 19:06:51 UTC 
Found the problem with Jan P.'s help. In the case of a user-installed
module, the SFS was in fact returning the writable filesystem the file
was defined on. However this was not quite what was wanted: it should
only do this in case the file is in fact in a writable subdelegate of
that filesystem, if the defining filesystem was a
ModuleLayeredFileSystem. Not really a modules bug as such, rather
projects system. Fixed in SystemFileSystem.java 1.19.
Comment 6 pzajac 2002-10-21 15:23:42 UTC 
verified
Comment 7 Quality Engineering 2003-07-01 16:18:56 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.