This document lists changes made to the XML tools
APIs. Please ask on the
mailing list if you have any questions about the details of a
change, or are wondering how to convert existing code to be compatible.
Ask there also for new backward compatible API enhancements.
No incompatible changes following version "1.0" should be introduced.
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.
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.api.xml/1 > 1.20
org.netbeans.spi.xml.cookiespackages were moved into a new module
CookieObserver.Messagestatic inner replaced by standalone
CookieObserverclass. New class is immutable.
CookieObserver.Messageturned into non-abstarct class.
sourcedo not throw
DataObjectfrom support classes were replaced by
Sourcerespectively. New class
DataObjectAdapterswas introduced to simplify providers.
Minimal XML tools API subset seems to be found. Asked
API gurus and
firstname.lastname@example.org> for its review.
The minimal subset consists of:
wrapInputSourcetaking one parameter.
ProcessorListenerremoved. It is moved to cookies as
getDefault(Lookup ctx)method. Now it is not needed, there are no clients until new projects scope lookups will be introduced.
UserCatalogtakes context parameter.
UserCatalogas original name have not been understood as User's.
SourceResolverwas not well evolvable.
UsersCatalogis a wrapper class consisting of set of methods each of them is by default implemented to indicate that its functionality is not provided by the default implementation.
UserCatalogProvideras original name have not been understood as User's.
UsersCatalogProviderintroduced to express what is role of SPI and what is client API.
AbstractUtilbecause it was not XML specifics. It should go to some general utility API such us OpenIDE util.
AbstractUtilwhich is used just for debugging and string localizing purposes.