<?xml version="1.0" encoding="UTF-8"?>
<!--
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.
-->
<!DOCTYPE api-answers PUBLIC "-//NetBeans//DTD Arch Answers//EN" "../../nbbuild/antsrc/org/netbeans/nbbuild/Arch.dtd" [
  <!ENTITY api-questions SYSTEM "../../nbbuild/antsrc/org/netbeans/nbbuild/Arch-api-questions.xml">
]>

<api-answers
  question-version="1.12"
  module="Autoupdate client"
  author="phrebejk@netbeans.org"
>

  &api-questions;


<!--
        
     <question id="arch-what">
            What is this project good for?
            <hint>
            Please provide here few lines describing the the project, 
            what problem it should solve, provide links to documentation, 
            specifications, etc.
            </hint>
        </question>
-->
<answer id="arch-what">
Autoupdate modules serves for keeping all parts of NetBeans instalation
up to date. It is capable of checking the AU server find any new and/or
updated modules download them and update the instalation.
It provides non-stable <api name="Autoupdate" type="export" category="friend" group="java"
  url="@org-netbeans-modules-autoupdate@/index.html" 
  />
api to allow integrations.

</answer>

<!--
        <question id="arch-overall" when="init">
            Describe the overall architecture. 
            <hint>
            What will be API for 
            <a href="http://openide.netbeans.org/tutorial/api-design.html#design.apiandspi" shape="rect">
                clients and what support API</a>? 
            What parts will be pluggable?
            How will plug-ins be registered? Please use <code>&lt;api type="export"/&gt;</code>
            to describe your general APIs.
            If possible please provide 
            simple diagrams. 
            </hint>
        </question>
<answer id="arch-overall">
XXX no answer for arch-overall
</answer>
-->





<!--
        <question id="arch-usecases" when="init">
            Describe the main <a href="http://openide.netbeans.org/tutorial/api-design.html#usecase" shape="rect">
            use cases</a> of the new API. Who will use it under
            what circumstances? What kind of code would typically need to be written
            to use the module?
        </question>
<answer id="arch-usecases">
XXX no answer for arch-usecases
</answer>
-->



<!--
        
     <question id="compat-i18n">
            Is your module correctly internationalized?
            <hint>
            Correct internationalization means that it obeys instuctions 
            at <a href="http://www.netbeans.org/devhome/docs/i18n/index.html">
            NetBeans I18N pages</a>.
            </hint>
        </question>
-->
    <answer id="compat-i18n">
        <p>
            Mostly. Internationalization and branding of the module itself
            (<samp>autoupdate.jar</samp>) is done in the regular NetBeans
            fashion, e.g. localized resources may be placed in
            <samp>modules/locale/autoupdate_f4j_ja.jar</samp>, etc. Support for
            the updater (<samp>updater.jar</samp>) is more idiosyncratic because
            it runs as a standalone application without access to the
            preconfigured NetBeans classpath and <code>NbBundle.branding</code>
            system. Therefore it supports internationalization and branding as
            follows:
        </p>
        <ul>
            <li>
                <p>
                    Localized and/or branded variants of the updater may be
                    placed in <samp>lib/locale/updater_*.jar</samp> as expected.
                </p>
            </li>
            <li>
                <p>
                    The file
                    <samp>org/netbeans/updater/resources/updatersplash.gif</samp>
                    may be branded in the regular way, e.g.
                    <samp>org/netbeans/updater/resources/updatersplash_f4j.gif</samp>.
                    But, it <strong>cannot currently be localized</strong>.
                </p>
                <p>
                    Note that the <code>-branding</code> startup parameter cannot
                    be used to specify branding for this, since that is
                    interpreted only by the IDE, but the standard
                    <code>lib/branding</code> file is parsed to determine the
                    installation's branding, which normally suffices. The failure
                    to interpret the startup parameter might be a problem if the
                    NetBeans platform were installed in one directory, different
                    IDE consolidations were installed in other directories, and a
                    special startup script used
                    <code>-J-Dnetbeans.dirs=...</code> and <code>-branding</code>
                    to create a branded unified IDE from them all.
                </p>
            </li>
            <li>
                <p>
                    The file <samp>org/netbeans/updater/Bundle.properties</samp>
                    can be localized in the regular way, e.g.
                    <samp>org/netbeans/updater/Bundle_ja.properties</samp>. But,
                    it <strong>cannot currently be branded</strong>.
                </p>
            </li>
            <li>
                <p>
                    Since branded splash screens may have different color
                    schemes, you can create a file
                    <samp>org/netbeans/updater/resources/Branding.properties</samp>
                    (<strong>note</strong> the lack of a standard branding
                    suffix!) in your branding JAR which may specify keys
                    (hopefully self-explanatory):
                </p>
                <ul>
                    <li><code>UpdaterFrame.TextBackground_R</code></li>
                    <li><code>UpdaterFrame.TextBackground_G</code></li>
                    <li><code>UpdaterFrame.TextBackground_B</code></li>
                    <li><code>UpdaterFrame.TextForeground_R</code></li>
                    <li><code>UpdaterFrame.TextForeground_G</code></li>
                    <li><code>UpdaterFrame.TextForeground_B</code></li>
                    <li><code>UpdaterFrame.hasBorder</code></li>
                </ul>
                <p>
                    Issuezilla #21624 may have more information on this weird
                    system.
                </p>
            </li>
        </ul>
    </answer>



<!--
        
     <question id="compat-standards">
            Does the module implement or define any standards? Is the 
            implementation exact or does it deviate somehow?
        </question>
-->
<answer id="compat-standards">
The module does not implement any standards. However it defines it's
own XML format for communication with the server and own packaging
format for modules. Detailed information about the XML at
<a href="@org-netbeans-modules-autoupdate@">autoupdate homepage</a>.
</answer>



<!--
        
     <question id="compat-version">
            Can your module coexist with earlier and future
            versions? Can you correctly read all old settings? Will future
            versions be able to read your current settings? Can you read
            or politely ignore settings stored by a future version?
            
            <hint>
            Very helpful for reading settings is to store version number
            there, so future versions can decide whether how to read/convert
            the settings and older versions can ignore the new ones.
            </hint>
        </question>
-->
<answer id="compat-version">
Yes
</answer>



<!--
        
     <question id="dep-jre">
            Which version of JRE do you need (1.2, 1.3, 1.4, etc.)?
            <hint>
            It is expected that if your module runs on 1.x that it will run 
            on 1.x+1 if no, state that please. Also describe here cases where
            you run different code on different versions of JRE and why.
            </hint>
        </question>
-->
<answer id="dep-jre">
1.3
</answer>



<!--
        
     <question id="dep-jrejdk">
            Do you require the JDK or is the JRE enough?
        </question>
-->
<answer id="dep-jrejdk">
JRE
</answer>



<!--
        
     <question id="dep-nb">
            What other NetBeans projects does this one depend on?
            <hint>
            If you want, describe such projects as imported API using
            the <code>&lt;api name="identification" type="import or export" category="stable" url="where is the description" /&gt;</code>
            </hint>
        </question>
-->
<answer id="dep-nb">
Depends on openide, namely
<api name="ModulesAPI" type="import" category="official" url="@org-openide-modules@/architecture-summary.html" group="java"/>,
<api name="FilesystemsAPI" type="import" category="official" url="@org-openide-filesystems@/architecture-summary.html" group="java"/>,
<api name="LoadersAPI" type="import" category="official" url="@org-openide-loaders@/architecture-summary.html" group="java"/>,
<api name="ExplorerAPI" type="import" category="official" url="@org-openide-explorer@/qarchitecture-summary.html" group="java"/>,
<api name="SettingsAPI" type="import" category="official" url="@org-openide-settings@/architecture-summary.html" group="java"/>,
<api name="UtilitiesAPI" type="import" category="official" url="@org-openide-util@/architecture-summary.html" group="java"/>,
<api name="LookupAPI" type="import" category="official" url="@org-openide-util@/org/openide/util/package-summary.html#package_description" group="java" />.

The autoupdate module also depends directly
on a couple of classes in the NetBeans core which are public specifically for its benefit:
<api name="org.netbeans.core.startup.AutomaticDependencies" type="import" group="java" category="friend" url="@org-netbeans-core-startup@/AutomaticDependencies.java"/>.
It depends on the layout of the NetBeans installation, most of which is implemented
by the module system in the NetBeans core.
It uses the file <api name="lib-ide.ks" group="java.io.File" type="export" category="devel">a cryptographic keystore for verifying
NBM signatures; this file is normally shipped with the NetBeans installation, currently
provided by nb4.0 cluster.</api> 
Finally <api name="updater.jar" group="java.io.File" type="export" category="friend">
is a file located at <code>platform4/module/ext/updater.jar</code> 
used by the NetBeans launcher that checks for this file and executes it 
in order to correctly implement the restart-with-updates if any updates are 
detected</api>.
The NetBeans launcher checks the directory <code>update/download</code> in order the userdir (e.g. ~/.netbeans/4.0/update/download/)
and also under each cluster (i.e. platform4, ide4 etc.). If any NBM found there then the IDE will restart after IDE's exit (first runs Updater, after starts next IDE session).
If there is aside this NBM also the file <code>install_later.xml</code> contains any NBM then the IDE doesn't restart automatically after exit
but the launcher will start the Updater when the IDE will start next time.

</answer>



<!--
        
     <question id="dep-non-nb">
            What other projects outside NetBeans does this one depend on?
            
            <hint>
            Some non-NetBeans projects are packaged as NetBeans modules
            (see <a href="http://libs.netbeans.org">libraries</a>) and
            it is prefered to use this approach when more modules may
            depend on such third-party library.
            </hint>
        </question>
-->
<answer id="dep-non-nb">
None
</answer>



<!--
        
     <question id="dep-platform">
            On which platforms does your module run? Does it run in the same
            way on each?
            <hint>
            If your module is using JNI or deals with special differences of
            OSes like filesystems, etc. please describe here what they are.
            </hint>
        </question>
-->
<answer id="dep-platform">
Any
</answer>



<!--
        
     <question id="deploy-jar">
            Do you deploy just module JAR file(s) or other files as well?
            <hint>
            If your module consist just from one module JAR file, just confirm that.
            If it uses more than one JAR, describe where there are located, how
            they refer to each other. 
            If it consist of module JAR(s) and other files, please describe
            what is their purpose, why other files are necessary. Please 
            make sure that installation/deinstallation leaves the system 
            in state as it was before installation.
            </hint>
        </question>
-->
<answer id="deploy-jar">
Autiupdate module is distributed as one .jar, but is accompanied by updater.jar
which is code which unpacks and installs downloaded modules (.nbms)
</answer>



<!--
        
     <question id="deploy-nbm">
            Can you deploy an NBM via the Update Center?
            <hint>
            If not why?
            </hint>
        </question>
-->
<answer id="deploy-nbm">
Yes
</answer>



<!--
        
     <question id="deploy-packages">
            Are packages of your module made inaccessible by not declaring them
            public?
            
            <hint>
            NetBeans module system allows restriction of access rights to
            public classes of your module from other modules. This prevents
            unwanted dependencies of others on your code and should be used
            whenever possible (<a href="http://www.netbeans.org/download/dev/javadoc/OpenAPIs/org/openide/doc-files/upgrade.html#3.4-public-packages">
            public packages
            </a>). 
            </hint>
        </question>
-->
<answer id="deploy-packages">
The module has no official public API. However it does NOT delare this explicitly
in the manifest using: "OpenIDE-Module-Public-Packages: -". The api is currently
used by the S1S autoupdate module. The separation of the official API/SPI 
should be done for 4.0. 
<api name="autoupdate-dtd" type="export" group="dtd" category="stable" url="@org-netbeans-modules-autoupdate@/nbm/catalog34.dtd"/>
<api name="info-dtd" type="export" category="stable" group="dtd" url="@org-netbeans-modules-autoupdate@/nbm/info34.dtd"/>

</answer>



<!--
        
     <question id="deploy-shared">
            Do you need to be installed in the shared location only, or in the user directory only,
            or can your module be installed anywhere?
            <hint>
            Installation location shall not matter, if it does explain why.
            Consider also whether <code>InstalledFileLocator</code> can help.
            </hint>
        </question>
-->
<answer id="deploy-shared">
In order to be able to update the whole NB platform the module has to be installed
in the shared directory. Also the updater jar is stored in the shared directory (
in the lib subdirectory.)
</answer>



<!--
        
     <question id="exec-classloader">
            Does your code create its own class loader(s)?
            <hint>
            A bit unusual. Please explain why and what for.
            </hint>
        </question>
-->
<answer id="exec-classloader">
No
</answer>



<!--
        
     <question id="exec-component">
            Is execution of your code influenced by any (string) property
            of any of your components?
            
            <hint>
            Often <code>JComponent.getClientProperty</code>, <code>Action.getValue</code>
            or <code>PropertyDescriptor.getValue</code>, etc. are used to influence
            a behaviour of some code. This of course forms an interface that should
            be documented. Also if one depends on some interface that an object
            implements (<code>component instanceof Runnable</code>) that forms an
            API as well.
            </hint>
        </question>
-->
<answer id="exec-component">
Uses getClientProperty( "Autoupdate_HelpID" ) in the AU Wizard.
</answer>



<!--
        
     <question id="exec-privateaccess">
            Are you aware of any other parts of the system calling some of 
            your methods by reflection?
            <hint>
            If so, describe the "contract" as an API. Likely private or friend one, but
            still API and consider rewrite of it.
            </hint>
        </question>
-->
<answer id="exec-privateaccess">
No
</answer>



<!--
        
     <question id="exec-property">
            Is execution of your code influenced by any environment or
            Java system (<code>System.getProperty</code>) property?
            
            <hint>
            If there is a property that can change the behaviour of your 
            code, somebody will likely use it. You should describe what it does 
            and the stability category of this API. You may use
            <pre>
                &lt;property name="id" category="private" &gt;
                    description of the property, where it is used, what it influence, etc.
                &lt;/property&gt;            
            </pre>
            </hint>
        </question>
-->
<answer id="exec-property">
Yes.
<api type="import" group="property" name="netbeans.user" category="standard"> both autoupdate module and updater</api>
<api type="import" group="property" name="netbeans.home" category="official"> both autoupdate module and updater</api>
<api type="import" group="property" name="file.separtor" category="standard"> both autoupdate module and updater</api>
<api type="import" group="property" name="os.name" category="standard"> updater only in UpdaterFrame</api>
<api type="import" group="property" name="java.home" category="standard"> updater only in ModuleUpdater</api>
<api type="import" group="property" name="path.separator" category="official"> updater inly in ModuleUpdater</api>
<api type="import" group="property" name="http.proxyHost" category="official"> Autoupdate module in Autoupdater</api>
<api type="import" group="property" name="http.proxyPort" category="official"> Autoupdate module in Autoupdater</api>
<api type="import" group="property" name="netbeans.system_http_proxy" category="devel"> Autoupdate module in Autoupdater</api>
<api type="export" group="property" name="netbeans.autoupdate.version" category="private"> Autoupdate module in XMLAutoupdateType</api>
<api type="export" group="property" name="netbeans.autoupdate.country" category="private"> Autoupdate module in XMLAutoupdateType</api>
<api type="export" group="property" name="netbeans.autoupdate.language" category="private"> Autoupdate module in XMLAutoupdateType</api>
<api type="export" group="property" name="netbeans.autoupdate.variant" category="private"> Autoupdate module in XMLAutoupdateType</api>
<api type="import" group="property" name="user.home" category="standard"> Autoupdate module in SelectModulesPanel</api>
</answer>



<!--
        
     <question id="exec-reflection">
            Does your code use Java Reflection to execute other code?
            <hint>
            This usually indicates a missing or unsufficient API in the other
            part of the system. If the other side is not aware of your dependency
            this contract can be easily broken.
            </hint>
        </question>
-->
<answer id="exec-reflection">
<ul>
<li>The XMLUtil class in Updater calls invokes XML related methods by reflection
dependent on the fact whether xerces or Sun parser is used.</li>
<li>The Autoupdater class in AU module reads the proxy settings of IDE
by reflection</li>
</ul>
</answer>



<!--
        
     <question id="format-clipboard">
            Which data flavors (if any) does your code read from or insert to
            the clipboard?
        </question>
-->
<answer id="format-clipboard">
None
</answer>



<!--
        
     <question id="format-dnd">
            Which protocols (if any) does your code understand during Drag &amp; Drop?
        </question>
-->
<answer id="format-dnd">
None
</answer>



<!--
        
     <question id="format-types">
            Which file formats (if any) does your code read or write on disk?
        </question>
-->
<answer id="format-types">
<ul>
<li>Autoupdate types inf form of XML settings format</li>
<li>Update tracking info in own XML format</li>
<li>Downloaded .nbm files (basically .jar files)</li>
</ul>
</answer>



<!--
        
     <question id="lookup-lookup">
            Does your module use <code>org.openide.util.Lookup</code>
            to find any components to communicate with? Which ones?
            
            <hint>
            Please describe the interfaces you are searching for, where 
            are defined, whether you are searching for just one or more of them,
            if the order is important, etc. Also clasify the stability of such
            API contract.
            </hint>
        </question>
-->
<answer id="lookup-lookup">
<ul>
<li>Searches for AutoupdateTypes declared in XML layer</li>
<li>Autoupdater class searches for ClassLoader to be able to invoke 
proxy settings method by reflection.</li>
<li>Autoupdater class searches for ModuleDescriptions using Lookup</li>
</ul>
</answer>



<!--
        
     <question id="lookup-register">
            Do you register anything into lookup for other code to find?
            <hint>
            Do you register using layer file or using <code>META-INF/services</code>?
            Who is supposed to find your component?
            </hint>
        </question>
-->
<answer id="lookup-register">
   The core module registers a implementation of <code>org.netbeans.core.StatusLineElementProvider</code> interface,
   it allows to display in the status line a notification about new available updates.
   It's registered by <code>META-INF/services</code>.
</answer>



<!--
        
     <question id="lookup-remove">
            Do you remove entries of other modules from lookup?
            <hint>
            Why? Of course, that is possible, but it can be dangerous. Is the module
            your are masking resource from aware of what you are doing?
            </hint>
        </question>
-->
<answer id="lookup-remove">
No
</answer>



<!--
        
     <question id="perf-exit">
            Does your module run any code on exit?
        </question>
-->
<answer id="perf-exit">
No. But notice that the AU sometimes itself invokes the IDE restart to 
install/update modules which require restart. 
</answer>



<!--
        
     <question id="perf-huge_dialogs">
            Does your module contain any dialogs or wizards with a large number of
            GUI controls such as combo boxes, lists, trees, or text areas?
        </question>
-->
<answer id="perf-huge_dialogs">
Yes there is an AU wizard which guides the user through the updating process.
(5-6 panels). The updater which unpcaks the modules has it's own form.
</answer>



<!--
        
     <question id="perf-limit">
            Are there any hardcoded or practical limits in the number or size of
            elements your code can handle?
        </question>
-->
<answer id="perf-limit">
No
</answer>



<!--
        
     <question id="perf-mem">
            How much memory does your component consume? Estimate
            with a relation to the number of windows, etc.
        </question>
-->
<answer id="perf-mem">
The memory usage of the AU depends on number of chcked update servers and 
on number of modules available on the server. However the memory
consumption should be decent (few instances of various objects per module)
</answer>



<!--
        
     <question id="perf-menus">
            Does your module use dynamically updated context menus, or
            context-sensitive actions with complicated enablement logic?
        </question>
-->
<answer id="perf-menus">
No.
</answer>



<!--
        
     <question id="perf-progress">
            Does your module execute any long-running tasks?
            <hint>Typically they are tasks like connecting over
            network, computing huge amount of data, compilation.
            Such communication should be done asynchronously (for example
            using <code>RequestProcessor</code>), definitively it should 
            not block AWT thread.
            </hint>
        </question>
-->
<answer id="perf-progress">
Yes. The autoupdate communicates with the update server over the network.
The communication usually consits of 1) downloading the module catalogue
from the server 2) optionaly some autentication communication (in case
of S1S update server). 3) Downloading the modules. Depending on number and 
size of modules users selects to install/update and depending on the brandwidth
the download can take long time.
</answer>



<!--
        
     <question id="perf-scale">
            Which external criteria influence the performance of your
            program (size of file in editor, number of files in menu, 
            in source directory, etc.) and how well your code scales?
            Please include some estimates.
        </question>
-->
<answer id="perf-scale">
Number of available update servers. Nuber of modules available on the servers
, nuber of installed modules. The scalability should be good. However there is
no caching/swapping mechanism i.e. all the information about modules is held
in memory during the update process (Notice that this does not mean that the
downloaded modules are held in memory)
</answer>



<!--
        
     <question id="perf-startup">
            Does your module run any code on startup?
        </question>
-->
<answer id="perf-startup">
Yes. It initilizes the autochecker. Autochecker is piece of code which
depending on user's setting automaticaly checks the autoupdate servers for 
updates on IDE startup.
</answer>



<!--
        
     <question id="perf-wakeup">
            Does any piece of your code wake up periodically and do something
            even when the system is otherwise idle (no user interaction)?
        </question>
-->
<answer id="perf-wakeup">
No. Only the autochecker checks the time of last update and the users settings to 
figure out whether to check servers for new updates. This happens only once on 
the IDE startup.
</answer>



<!--
        
     <question id="resources-file">
            Does your module use <code>java.io.File</code> directly?
            
            <hint>
            NetBeans provide a logical wrapper over plain files called 
            <code>org.openide.filesystems.FileObject</code> that
            provides uniform access to such resources and is the prefered
            way that should be used. But of course there can be situations when
            this is not suitable.
            </hint>
        </question>
-->
<answer id="resources-file">
<p>
<api name="autoupdate-keystore" type="export" group="java.io.File" category="private">
There are two keystores in the netbeans installation. One in the lib
directory of NetBeans root dir. Second is in the lib directory of the
user's dir.<br/>
First one contains the default public key and ceritificate distributed 
with NetBeans, which is used for signing modules on the NetBeans autoupdate 
server. Certificates are added into the keystore when the autoupdate runs
in the root mode. This means that the root user of NetBeans may add certificates
for other users.<br/>
Second keystore is used for user additions of certificated. I.e. when the 
user decides to trust some certificate and adds it into the keystore then
the cerificate is added into his personal keystore and does not affect other
users of the NetBeans installation. Keystore format is in binary form.
</api>
</p>
<p>
<api name="autoupdate-backup" type="export" group="java.io.File" category="private">
There is no support for getting back to older versions of modules using the
NetBeans UI. However the autoupdate client does backup of all files it 
replaces into update/backup subdirectory of either NetBeans root or NetBeans
user directory (depends on the mode NetBeans IDE is run in). 
Content backup is in private binary form.
</api>
<api name="autoupdate-tracking" type="export" group="java.io.File" category="friend">
Autoupdate client
also keeps track of the changes made into the installation in the
update_tracking subdirectory of NetBeans directory. There is XML file per
NetBeans module.<br/>
It is possible to do manual backout of installed modules using the files backed
up in the backup directory and the information stored in the update_tracking 
directory. The update tracking is used by other parts of the system (like
apisupport) and thus is exposed as a friend API.
</api>
The autoupdate searches for 
<api name=".noautoupdate" type="export" group="java.io.File" category="friend">
file that can be located in a root of a cluster. If it is present then 
the cluster cannot be managed by the autoupdate system. This is useful
in case of RPM distribution which have their own way of managing 
libraries and do not want collisions with autoupdate.
</api>
</p>

</answer>


<!--
        
     <question id="resources-layer">
            Does your module provide own layer? Does it create any files or
            folders in it? What it is trying to communicate by that and with which 
            components?
            
            <hint>
            NetBeans allows automatic and declarative installation of resources 
            by module layers. Module register files into appropriate places
            and other components use that information to perform their task
            (build menu, toolbar, window layout, list of templates, set of
            options, etc.). 
            </hint>
        </question>
-->
<answer id="resources-layer">
Yes. It uses it's own XML layer to install actions, menu items, wizard and
settings. Also a template for the standard netbeans Au server is installed
using the XML layer.
It also installs the default update centers by registering instances of AU 
service type. Same thing is done by the S1S AU extension. These settings
are stored on the DefaultFilesystmem in the Services/AutoupdateType folder. 
Autoupdate types are standard .settings files. However to initialize the server
directly from the layer one can use the url_key and enabled attributes of the
file. First one points to key in the localizing bundle which contains URL
of the server. The second allows for enablig/disabling the server by
default.
<api name="autoupdate-type" type="export" category="stable" group="layer"/>
</answer>



<!--
        
     <question id="resources-mask">
            Does your module mask/hide/override any resources provided by other modules in
            their layers?
            
            <hint>
            If you mask a file provided by another module, you probably depend
            on that and do not want the other module to (for example) change
            the file's name. That module shall thus make that file available as an API
            of some stability category.
            </hint>
        </question>
-->
<answer id="resources-mask">
No
</answer>



<!--
        
     <question id="resources-read">
            Does your module read any resources from layers? For what purpose?
            
            <hint>
            As this is some kind of intermodule dependency, it is a kind of API.
            Please describe it and clasify according to 
            <a href="http://openide.netbeans.org/tutorial/api-design.html#categories">
            common stability categories</a>.
            </hint>
        </question>
-->
<answer id="resources-read">
Yes. Modules may register their update server types and templates for these 
service types in the xml-layer. This is done by the S1S au extension. 
This API should probably be rated as under-development.
The autoupdate-type is described in the resources-leayer question beside this
anmd mentioned menus and action template for autoupdate type is registered in the 
layer. Users may use this template for adding extra AU servers into the 
AU client.

<api name="Loaders-application-x-nbm-Actions" category="stable" group="layer" type="export" />
The actions that the <code>NbmDataLoader</code> shows in its popup menu are read from
a layer folder <code>Loaders/application/x-nbm/Actions</code>.

</answer>

<!--
        
     <question id="keystores">
            Is keystore per user or common?
            
            <hint>
            Additional qustion from the ARC team.
            </hint>
        </question>
-->

<!--
        <question id="exec-introspection">
            Does your module use any kind of runtime type information (<code>instanceof</code>,
            work with <code>java.lang.Class</code>, etc.)?
            <hint>
            Check for cases when you have an object of type A and you also
            expect it to (possibly) be of type B and do some special action. That
            should be documented. The same applies on operations in meta-level
            (Class.isInstance(...), Class.isAssignableFrom(...), etc.).
            </hint>
        </question>
-->
<answer id="exec-introspection">
Of course. For internal types.
</answer>



<!--
        <question id="exec-process">
            Do you execute an external process from your module? How do you ensure
            that the result is the same on different platforms? Do you parse output?
            Do you depend on result code?
            <hint>
            If you feed an input, parse the output please declare that as an API.
            </hint>
        </question>
-->
<answer id="exec-process">
No.
</answer>









<!--
        <question id="arch-overall" when="init">
            Describe the overall architecture. 
            <hint>
            What will be API for 
            <a href="http://openide.netbeans.org/tutorial/api-design.html#design.apiandspi" shape="rect">
                clients and what support API</a>? 
            What parts will be pluggable?
            How will plug-ins be registered? Please use <code>&lt;api type="export"/&gt;</code>
            to describe your general APIs.
            If possible please provide 
            simple diagrams. 
            </hint>
        </question>
-->
 <answer id="arch-overall">
  <p>
   XXX no answer for arch-overall
  </p>
 </answer>



<!--
        <question id="arch-quality" when="init">
            How will the <a href="http://www.netbeans.org/community/guidelines/q-evangelism.html" shape="rect">quality</a>
            of your code be tested and 
            how are future regressions going to be prevented?
            <hint>
            What kind of testing do
            you want to use? How much functionality, in which areas,
            should be covered by the tests? 
            </hint>
        </question>
-->
 <answer id="arch-quality">
  <p>
   XXX no answer for arch-quality
  </p>
 </answer>



<!--
        <question id="arch-time" when="init">
            What are the time estimates of the work?
            <hint>
            Please express your estimates of how long the design, implementation,
            stabilization are likely to last. How many people will be needed to
            implement this and what is the expected milestone by which the work should be 
            ready?
            </hint>
        </question>
-->
 <answer id="arch-time">
  <p>
   XXX no answer for arch-time
  </p>
 </answer>



<!--
        <question id="arch-usecases" when="init">
            <hint>
                Content of this answer will be displayed as part of page at
                http://www.netbeans.org/download/dev/javadoc/usecases.html 
                You can use tags &lt;usecase name="name&gt; regular html description &lt;/usecase&gt;
                and if you want to use an URL you can prefix if with @TOP@ to begin
                at the root of your javadoc
            </hint>
        
            Describe the main <a href="http://openide.netbeans.org/tutorial/api-design.html#usecase" shape="rect">
            use cases</a> of the new API. Who will use it under
            what circumstances? What kind of code would typically need to be written
            to use the module?
        </question>
-->
 <answer id="arch-usecases">
  <p>
   XXX no answer for arch-usecases
  </p>
 </answer>



<!--
        <question id="arch-where" when="init">
            Where one can find sources for your module?
            <hint>
                Please provide link to the CVS web client at
                http://www.netbeans.org/download/source_browse.html
                or just use tag defaultanswer generate='here'
            </hint>
        </question>
-->
 <answer id="arch-where">
  <defaultanswer generate='here' />
 </answer>



<!--
        <question id="deploy-dependencies" when="final">
            What do other modules need to do to declare a dependency on this one?
            <hint>
                Provide a sample of the actual lines you would add to a module manifest
                to declare a dependency, for example using OpenIDE-Module-Module-Dependencies
                or OpenIDE-Module-Requires. You may use the magic token @SPECIFICATION-VERSION@
                to represent the current specification version of the module.
            </hint>
        </question>
-->
 <answer id="deploy-dependencies">
  <p>
   XXX no answer for deploy-dependencies
  </p>
 </answer>



<!--
        <question id="exec-ant-tasks" when="impl">
            Do you define or register any ant tasks that other can use?
            
            <hint>
            If you provide an ant task that users can use, you need to be very
            careful about its syntax and behaviour, as it most likely forms an
	          API for end users and as there is a lot of end users, their reaction
            when such API gets broken can be pretty strong.
            </hint>
        </question>
-->
 <answer id="exec-ant-tasks">
  <p>
   XXX no answer for exec-ant-tasks
  </p>
 </answer>



<!--
        <question id="exec-threading" when="impl">
            What threading models, if any, does your module adhere to?
            <hint>
                If your module calls foreign APIs which have a specific threading model,
                indicate how you comply with the requirements for multithreaded access
                (synchronization, mutexes, etc.) applicable to those APIs.
                If your module defines any APIs, or has complex internal structures
                that might be used from multiple threads, declare how you protect
                data against concurrent access, race conditions, deadlocks, etc.,
                and whether such rules are enforced by runtime warnings, errors, assertions, etc.
                Examples: a class might be non-thread-safe (like Java Collections); might
                be fully thread-safe (internal locking); might require access through a mutex
                (and may or may not automatically acquire that mutex on behalf of a client method);
                might be able to run only in the event queue; etc.
                Also describe when any events are fired: synchronously, asynchronously, etc.
                Ideas: <a href="http://core.netbeans.org/proposals/threading/index.html#recommendations" shape="rect">Threading Recommendations</a> (in progress)
            </hint>
        </question>
-->
 <answer id="exec-threading">
  <p>
   XXX no answer for exec-threading
  </p>
 </answer>



<!--
        <question id="perf-spi" when="init">
            How the performance of the plugged in code will be enforced?
            <hint>
            If you allow foreign code to be plugged into your own module, how
            do you enforce that it will behave correctly and quickly and will not
            negatively influence the performance of your own module?
            </hint>
        </question>
-->
 <answer id="perf-spi">
  <p>
   XXX no answer for perf-spi
  </p>
 </answer>



<!--
        <question id="security-grant" when="final">
            Does your code grant additional rights to some other code?
            <hint>Avoid using a class loader that adds extra
            permissions to loaded code unless really necessary.
            Also note that your API implementation
            can also expose unneeded permissions to enemy code by
            calling AccessController.doPrivileged().</hint>
        </question>
-->
 <answer id="security-grant">
  <p>
   XXX no answer for security-grant
  </p>
 </answer>



<!--
        <question id="security-policy" when="final">
            Does your functionality require modifications to the standard policy file?
            <hint>Your code might pass control to third-party code not
            coming from trusted domains. This could be code downloaded over the
            network or code coming from libraries that are not bundled
            with NetBeans. Which permissions need to be granted to which domains?</hint>
        </question>
-->
 <answer id="security-policy">
  <p>
   XXX no answer for security-policy
  </p>
 </answer>

</api-answers>
