|
This guide, Netscape Application Server Foundation Class Reference (Java), provides information on the NAS API. If you want to develop an application that is 100% compliant with the industry-standard Java technologies (servlets, JSPs, EJBs, and JDBC calls), do not use the NAS API.
However, there are three main situations for which the NAS API is useful.
These uses are described in the following subsections.
Additional NAS Features
In many situations, you'd like your application to use functionality that is not supported by the industry-standard APIs (for example, application events, security, and distributed state).
In addition, your application may need to access
For these situations, you may want to use the features listed in the following table:
The Development Environment of Netscape Application Builder
If you develop applications using Netscape Application Builder (NAB), your generated code may rely on the classes or interfaces listed in the following table. Typically, only NAB users will use these classes or interfaces, although they are available to anyone developing applications in the NAS environment.
Deprecated Functionality
Netscape Application Server now supports a standards-based application model. As a result, many of the classes and interfaces in the NAS Foundation Class Library are deprecated. They are provided only for backward compatibility with existing NAS applications.
Deprecated code will become unsupported in an upcoming release. Netscape therefore recommends that new applications use equivalent functionality from the industry-standard Java APIs. In many cases, you may want to migrate existing applications, so that they operate within the new application model. For more information, see the Migration Guide.
The following classes and interfaces of the NAS API are deprecated. Within this reference guide, the corresponding headings are marked (deprecated).
|
Previous
