<?xml version="1.0" encoding="UTF-8"?>

<!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.24"

author="dkonecny@netbeans.org"

>

&api-questions;

<answer id="arch-overall">

<p>

J2SE development support for freeform project.

</p>

<api group="java" name="JavaFreeformProjectSPI" type="export" category="friend">

<p>

Provides support SPI for instantiating this extension, e.g. Web freeform

extension can use it as part of its project wizard to set up new freeform

project with both Web and J2SE development support enabled.

</p>

</api>

<p>

The behavior of this extension is entirely controlled by

<code>project.xml</code>:

</p>

<ol>

<li>

<api group="dtd" name="freeform-project-java.xsd" type="export" category="official" url="http://www.netbeans.org/ns/freeform-project-java/1.xsd">

<p>

Old XML schema for the Java-specific section. Users are allowed

to modify this section by hand and can refer to this schema for available

syntax.

</p>

</api>

</li>

<li>

<api group="dtd" name="freeform-project-java-2.xsd" type="export" category="official" url="http://www.netbeans.org/ns/freeform-project-java/2.xsd">

<p>

Current XML schema for the Java-specific section.

</p>

</api>

</li>

</ol>

</answer>

<answer id="arch-quality">

<p>

Unit test coverage should be high, except for the GUI portions which may be

covered by functional tests in the future.

</p>

</answer>

<answer id="arch-time">

<p>

Complete.

</p>

</answer>

<answer id="arch-usecases">

<p>

See the <a

href="http://projects.netbeans.org/buildsys/design.html#freeform">Architecture

Sketch</a> for justifications of the module.

</p>

</answer>

<answer id="arch-what">

<p>

This module implements J2SE development support in Freeform project type.

See Freeform project type documentation for its general description. The

main features of this extension are:

</p>

<ol>

<li>

<p>

Provides <code>packages</code> style view of source folder.

</p>

</li>

<li>

<p>

Answers various Java specific <dfn>queries</dfn> like classpath to use

for source files for purposes of code completion and refactoring, source

level to use for source files, etc.

</p>

</li>

<li>

<p>

Provides wizard to help the user set up a new project with J2SE support.

</p>

</li>

</ol>

<p>

Specifications:

</p>

<ol>

<li>

<a href="http://projects.netbeans.org/buildsys/freeform-project-ui-spec.html">UI Specification</a>

</li>

<li>

<a href="http://projects.netbeans.org/buildsys/design.html#freeform">Architecture Sketch</a>

</li>

</ol>

</answer>

<answer id="compat-i18n">

<p>

Yes.

</p>

</answer>

<answer id="compat-standards">

<p>

Defines project syntax of J2SE support. There is no known independent format for this.

</p>

</answer>

<answer id="compat-version">

<p>

Project XML schemas namespaces are versioned.

</p>

</answer>

<answer id="dep-jre">

<p>

1.4+.

</p>

</answer>

<answer id="dep-jrejdk">

<p>

JRE.

</p>

</answer>

<answer id="dep-nb">

<ul>

<li>

<api group="java" name="FreeformProjectSPI" type="import" category="friend">

<p>

Base Freeform SPI.

</p>

</api>

</li>

<li>

<api group="java" name="AntProjectAPI" type="import" category="official">

<p>

The SPI is used heavily to implement various queries, evaluate Ant

properties at development time, etc.

</p>

</api>

</li>

<li>

<api group="java" name="JavaSupportAPIs" type="import" category="official">

<p>

Implements the classpath query.

</p>

</api>

</li>

<li>

<api group="java" name="JavaPlatformAPI" type="import" category="official">

<p>

Looks for registered Java platforms to handle the boot classpath.

</p>

</api>

</li>

<li>

<api group="java" name="JavaProjectAPI" type="import" category="official">

<p>

Used for the Java package view, etc.

</p>

</api>

</li>

<li>

<api group="java" name="ProjectAPI" type="import" category="official">

<p>

Basic project API.

</p>

</api>

</li>

<li>

<api group="java" name="ProjectUIAPI" type="import" category="official">

<p>

Used to register the project open hook, etc.

</p>

</api>

</li>

<li>

<api group="java" name="GeneralQueriesAPI" type="import" category="official">

<p>

For checking file collocation.

</p>

</api>

</li>

<li>

<api group="java" name="Filesystems" type="import" category="official">

<p>

Used for many purposes.

</p>

</api>

</li>

<li>

<api group="java" name="Nodes" type="import" category="official">

<p>

Used to show the logical view.

</p>

</api>

</li>

<li>

<api group="java" name="Wizards" type="import" category="official">

<p>

For the new project wizards.

</p>

</api>

</li>

</ul>

</answer>

<answer id="dep-non-nb">

<p>

None. (Implicitly Apache Ant.)

</p>

</answer>

<answer id="dep-platform">

<p>

Any.

</p>

</answer>

<answer id="deploy-dependencies">

Nothing.

</answer>

<answer id="deploy-jar">

<p>

Just a JAR.

</p>

</answer>

<answer id="deploy-nbm">

<p>

Yes.

</p>

</answer>

<answer id="deploy-packages">

<p>

Only official SPI packages are exported (and only to friend modules).

</p>

</answer>

<answer id="deploy-shared">

<p>

Anywhere.

</p>

</answer>

<answer id="exec-classloader">

<p>

No.

</p>

</answer>

<answer id="exec-component">

<p>

No.

</p>

</answer>

<answer id="exec-introspection">

<p>

No.

</p>

</answer>

<answer id="exec-privateaccess">

<p>

No.

</p>

</answer>

<answer id="exec-process">

<p>

No.

</p>

</answer>

<answer id="exec-property">

<p>

No.

</p>

</answer>

<answer id="exec-reflection">

<p>

No.

</p>

</answer>

<answer id="exec-threading">

<p>

Uses <code>ProjectManager.mutex()</code> in some cases. Mostly depends on

threading model of queries. EQ for GUI things of course.

</p>

</answer>

<answer id="format-clipboard">

<p>

None.

</p>

</answer>

<answer id="format-dnd">

<p>

None.

</p>

</answer>

<answer id="format-types">

<p>

None.

</p>

</answer>

<answer id="lookup-lookup">

<p>

Just usual <code>getDefault</code> methods.

</p>

</answer>

<answer id="lookup-register">

<p>

Implementation of <code>ProjectNature</code> is registered in <code>META-INF/services</code>.

</p>

</answer>

<answer id="lookup-remove">

<p>

No.

</p>

</answer>

<answer id="perf-exit">

<p>

No.

</p>

</answer>

<answer id="perf-huge_dialogs">

<p>

No. There are two customizer panels which are provided by this

extension and which are part of Freeform project customizer, but they

are of reasonable size.

</p>

</answer>

<answer id="perf-limit">

<p>

None in particular.

</p>

</answer>

<answer id="perf-mem">

<p>

Unknown; probably small.

</p>

</answer>

<answer id="perf-menus">

<p>

No.

</p>

</answer>

<answer id="perf-progress">

<p>

No.

</p>

</answer>

<answer id="perf-scale">

<p>

Nothing known.

</p>

</answer>

<answer id="perf-spi">

<p>

N/A

</p>

</answer>

<answer id="perf-startup">

<p>

No.

</p>

</answer>

<answer id="perf-wakeup">

<p>

No.

</p>

</answer>

<answer id="resources-file">

<p>

Where needed to evaluate Ant properties or satisfy queries.

</p>

</answer>

<answer id="resources-layer">

<p>

Registers new project wizards.

</p>

</answer>

<answer id="resources-mask">

<p>

No.

</p>

</answer>