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.
(1) The more interesting one is that while projectObject.getContext().bind() will write to the area specific to that projectObject, (Context)projectObject.getContext().lookup(subcontextName).bind() will bind the setting object to whatever of the merged Contexts from parent Organizers, that defined the subcontext rather than to the projectObject-specific context. (2) It's worth at least documenting that one should avoid calling setObject on Binding returned from the ProjectObject's settings Context. If used, it will overwrite that particular definition of the setting, possibly bound to the context of a parent Organizer, rather than write to the ProjectObject's own context, hiding the former definition.
The #1 is fixed already, the Context returned from ProjectMember.getContext doesn't allow to traverse outside of it when using lookup method. The #2 is still pending and seems to be serious defect.
The ProxyContext.list* methods return correct enumerations now. They work following way: A. The list*("") provides 'flat list' of bindings from all contexts in the stack, but each binding is listed only once. It means that binding from lower layer is hidden by the binding from the highest layer containing the bining B. The list*("someName") provides the 'deep list' of bindings across all layers containing the bining, each element of the list has empty name. All elemets in both cases don't allow modifications, that means the set* methods will fail with UOE.
Verified
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as CLOSED.