站内搜索: 请输入搜索关键词
当前页面: 在线文档首页 > NetBeans API Javadoc (Current Development Version)

Change History for the Registry API - NetBeans API Javadoc (Current Development Version)

Introduction

This document lists changes made to the Registry API.


Index of APIs

Incompatible changes by date

Fuller descriptions of all changes can be found below (follow links).

Not all deprecations are listed here, assuming that the deprecated APIs continue to essentially work. For a full deprecation list, please consult the Javadoc.

All changes by date

Changes by version

These API specification versions may be used to indicate that a module requires a certain API feature in order to function. For example, if you see here a feature you need which is labelled 1.20, your manifest should contain in its main attributes the line:

OpenIDE-Module-Module-Dependencies: org.netbeans.modules.registry > 1.20

Changes by affected class

org.netbeans.spi.registry.BasicContext

org.netbeans.api.registry.Context

org.netbeans.spi.registry.MergedContextProvider

org.netbeans.api.registry.ObjectRef

org.netbeans.spi.registry.RootContext

org.netbeans.spi.registry.SpiUtils


Details of all changes by API and date


Registry API

A few compatible and incompatible changes

Dec 18 '03; API spec. version: 1.7; affected top-level classes: Context ObjectRef org.netbeans.spi.registry.RootContext SpiUtils BasicContext; made by: rmatous; issues: #38109
A few compatible and incompatible changes:

There is waste of time to traverse to root whenever is root necessary. But there is missing convenient getRootContext method (see also getAbsoluteContextName() that returns full path from the root context).

A little confusing constructor for ObjectRef replaced with two constructors.

In RootContext are all 3 methods optional and can throw UnsupportedOperationException. Method flush was never implemented and method getMutex won't be necessary beacuse just one Mutext will be shared for all Contexts. Method findObject could be used for backward compatibility replacing current autosave functionality but its not vital and can be ommited. So I suggest to remove RootContex from API.

Added ability to create merged Contexts

Sep 18 '03; API spec. version: 1.6; affected top-level classes: Context SpiUtils MergedContextProvider; made by: rmatous; issues: #34057
Following API changes was made to provide ability to create merged Contexts:
Subcontext, bindings and attributes for context are merged according their names overtaken from their delegates.

SPIUtils.createRootContext(Map) removed

Jun 12 '03; API spec. version: 1.5; made by: dkonecny; issues: #34342
SPIUtils.createRootContext(Map) method will be removed. Use method org.netbeans.api.registry.fs.FileSystemContextFactory.createContext(FileObject) from core/registry module instead. It is possible that this method is already in use and so it was left in the API for week or two with warning message. Remove its usage immediatelly because it will be removed very soon, definitely before release.

Context.getOrderedNames() added

Jun 11 '03; API spec. version: 1.4; made by: dkonecny; issues: #34274
Context.getOrderedNames() method was added and allows listing of names of ordered items of the context. See method JavaDoc for more details.

AttributeEvent.getAttributeName() can return null

Jun 5 '03; API spec. version: 1.3; made by: dkonecny
AttributeEvent.getAttributeName() can return null. It can happen when concrete source of the change was not clear. Client should reexamine all attributes.

A few compatible and incompatible changes

May 23 '03; API spec. version: 1.2; made by: dkonecny
A few compatible and incompatible changes:

Built on May 28 2007.  |  Portions Copyright 1997-2007 Sun Microsystems, Inc. All rights reserved.