An important concept with the JDeveloper data model is that of configurable components. Projects use configurable components to provide plugin support for features. The base project class, {@link oracle.jdeveloper.model.JProject}, provides a minimal set of properties. Additional properties are grouped within specific configurable components. For example, a configurable component provides the Javadoc settings stored within the project. Configurable components can be common, as is the case for the project paths, or based on specific configurations, as is the case for compiler settings. Note that configurable components do not have to implement any particular interfaces; instead, they are identified as configurable components automatically when they are added to the project data model.

In addition to the base {@link oracle.jdeveloper.model.JProject} class, the oracle.jdeveloper.model package provides a few configurable components and the user interface to modify them. Additional configurable components can be added to a project dynamically, as can the UI to modify the contents of the configurable components. The {@link oracle.jdeveloper.model.JProjectSettings} class can be used to register common components, and the {@link oracle.jdeveloper.model.JProjectConfiguration} class can be used to register configuration specific components.

The oracle.jdeveloper.model package defines {@link oracle.ide.model.Node} implementations for specific types of data. These types include Java sources ({@link oracle.jdeveloper.model.JavaSourceNode}) and classes ({@link oracle.jdeveloper.model.JavaClassNode}), JSP files ({@link oracle.jdeveloper.model.JspSourceNode}), images ({@link oracle.jdeveloper.model.ImageNode}), and SQLJ classes ({@link oracle.jdeveloper.model.SqljSourceNode}).

Related Documentation

See Extending JDeveloper Using the Addin API for detailed information.