<?xml version="1.0" encoding="UTF-8"?><!-- -*- sgml-indent-step: 2 -*- -->
<!--
   - The contents of this file are subject to the terms of the Common Development
   - and Distribution License (the License). You may not use this file except in
   - compliance with the License.
   - 
   - You can obtain a copy of the License at http://www.netbeans.org/cddl.html
   - or http://www.netbeans.org/cddl.txt.
   - 
   - When distributing Covered Code, include this CDDL Header Notice in each file
   - and include the License file at http://www.netbeans.org/cddl.txt.
   - If applicable, add the following below the CDDL Header, with the fields
   - enclosed by brackets [] replaced by your own identifying information:
   - "Portions Copyrighted [year] [name of copyright owner]"
   - 
   - The Original Software is NetBeans. The Initial Developer of the Original
   - Software is Sun Microsystems, Inc. Portions Copyright 1997-2006 Sun
   - Microsystems, Inc. All Rights Reserved.
  -->
<?xml-stylesheet type="text/xml" href="../../../../../nbbuild/javadoctools/apichanges.xsl"?>
<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../../../../../nbbuild/javadoctools/apichanges.dtd">

<!--

INFO FOR PEOPLE ADDING CHANGES:

Check the DTD (apichanges.dtd) for details on the syntax. You do not
need to regenerate the HTML, this will be done periodically; just
change the XML. If you can, validate the XML against the DTD, if not
do not worry about it. Rough syntax of a change (several parts optional):

<change>
    <api name="compiler"/>
    <summary>Some brief description here, can use <b>XHTML</b></summary>
    <version major="1" minor="99"/>
    <date day="13" month="6" year="2001"/>
    <author login="jrhacker"/>
    <compatibility addition="yes"/>
    <description>
        The main description of the change here.
        Again can use full <b>XHTML</b> as needed.
    </description>
    <class package="org.openide.compiler" name="DoWhatIWantCompiler"/>
    <issue number="14309"/>
</change>

Also permitted elements: <package>, <branch>. <version> is API spec
version, recommended for all new changes. <compatibility> should say
if things were added/modified/deprecated/etc. and give all information
related to upgrading old code. List affected top-level classes and
link to issue numbers if applicable. See the DTD for more details.

Changes need not be in any particular order, they are sorted in various
ways by the stylesheet anyway.

Dates are assumed to mean "on the trunk". If you *also* make the same
change on a stabilization branch, use the <branch> tag to indicate this
and explain why the change was made on a branch in the <description>.

Please only change this file on the trunk! Rather: you can change it
on branches if you want, but these changes will be ignored; only the
trunk version of this file is important.

Deprecations do not count as incompatible, assuming that code using the
deprecated calls continues to see their documented behavior. But do
specify deprecation="yes" in <compatibility>.

This file is not a replacement for Javadoc: it is intended to list changes,
not describe the complete current behavior, for which ordinary documentation
is the proper place.

-->

<apichanges>

  <!-- First, a list of API names you may use: -->
  <apidefs>
    <!-- org.netbeans.spi.settings -->
    <apidef name="settings_spi">Settings SPI</apidef>
    <!-- org.netbeans.api.settings -->
    <apidef name="settings_api">Settings API</apidef>
  </apidefs>

<!-- ACTUAL CHANGES BEGIN HERE: -->
  <changes>
    <change>
        <api name="settings_spi"/>
        <summary>Added DOMConvertor supporting composed content</summary>
        <version major="1" minor="1"/>
        <date day="22" month="8" year="2002"/>
        <author login="jpokorsky"/>
        <compatibility addition="yes"/>
        <description> Allow to reuse already written convertors 
            by newly created ones to facilitate a storing of complex objects.  
        </description>
        <class package="org.netbeans.spi.settings" name="DOMConvertor"/>
        <issue number="26284"/>
    </change>
    <change>
        <api name="settings_spi"/>
        <summary>Provide context to convertors</summary>
        <version major="1" minor="2"/>
        <date day="3" month="9" year="2002"/>
        <author login="jpokorsky"/>
        <compatibility addition="yes"/>
        <description> Get a context associated with the reader. 
            It can contain various info like a file location of the read object etc.
        </description>
        <class package="org.netbeans.spi.settings" name="Convertor"/>
        <class package="org.netbeans.spi.settings" name="DOMConvertor"/>
        <issue number="26076"/>
    </change>
  </changes>


  <!-- Now the surrounding HTML text and document structure: -->

  <htmlcontents>
<!--

                            NO NO NO NO NO!

         ==============>    DO NOT EDIT ME!  <======================

          AUTOMATICALLY GENERATED FROM APICHANGES.XML, DO NOT EDIT

                SEE core/settings/api/doc/changes/apichanges.xml

-->
    <head>
      <title>Settings API/SPI Changes by Date</title>
      <link rel="stylesheet" href="prose.css" type="text/css"/>
    </head>
    <body>
<!-- The actual lists of changes, as summaries and details: -->

      <p class="overviewlink"><a href="@TOP@/overview-summary.html">Overview</a></p>

      <standard-changelists module-code-name="org.netbeans.modules.settings/1"/>

      <hr/><p>@FOOTER@</p>

    </body>
  </htmlcontents>

</apichanges>
