Creating a Project

Nexaweb Studio offers the following project configurations:

Project Type	Server Type	Description
Nexaweb Ajax Client	Nexaweb Server	Creates a client that runs HTML/JavaScript, Nexaweb server functionality and services including the Nexaweb Internet Messaging Bus (IMB), and dynamic Java EE resources.
Nexaweb Ajax Client	Alternate Server	Creates a client that runs HTML/JavaScript and dynamic Java EE resources.
Nexaweb Java Client	Nexaweb Server	Creates a client that runs Java applets, Nexaweb server functionality and services including the Nexaweb Internet Messaging Bus (IMB), and dynamic Java EE resources.
Nexaweb Java Client	Alternate Server	Creates a client that runs Java applets and dynamic Java EE resources.
Nexaweb Java Plug-in	Nexaweb Server or Alternate Server	See Creating a Plug-in.

To create a new Nexaweb application project, follow these steps:

Note: The first time that you start Nexaweb Studio, the Welcome to Nexaweb Studio perspective appears.

1. Either:

From *Welcome to Nexaweb Studio* perspective:	From *Nexaweb* perspective:
Click Create a New Project.	Select File > New > Nexaweb Application Project.

The New Nexaweb Application wizard starts as shown in Figure 3.

2. Complete the first dialog of the New Nexaweb Application wizard as follows:

$image\img00319.gif$

Figure 3: New Nexaweb Application wizard.

Client: Click the checkbox beside the type of client to use for this project.

Nexaweb Ajax Client – creates a client that runs HTML/JavaScript
Nexaweb Java Client – create a client that runs Java applets

Server: Click the checkbox beside the type of server to use for this project.

Nexaweb Server – creates a Nexaweb Java EE server application, including Nexaweb server functionality.
Alternate Server – creates a standard Java EE server application with standard Java EE functionality only.

Click Next.
A Project Settings dialog appears.

3. Complete the Project Settings dialog as follows:

$image\img00320.gif$

Figure 4: Nexaweb New Application wizard.

Project Name: Specify a name to use for this project in the Eclipse Workspace. Studio uses this as the default Context Root and subdirectory for the project.

Project contents: Specifies the physical location of the application files. By default, the Eclipse default workspace. To specify another physical location for this application, click the Use default check box to de-select it, and specify the directory to use in the Directory field.

Target runtime: Specifies the application server runtime on which to develop this application and to use to compile the project at build time. The project uses libraries from this server. Nexaweb Studio includes Apache Tomcat as a default runtime for development.

To add a different target runtime now, click New. The New Server Runtime dialog appears.
Note: You can specify a target runtime when you want to run the project.

- Click + beside Apache/Tomcat (whichever version you installed) to expand the list.

- Click on the version of the server installed on your system and click next. The Tomcat server configuration dialog appears.

- Enter the Tomcat installation directory in the Tomcat installation directory field or click Browse to search for it.

- Specify in the JRE field a JRE located under the root directory of a JDK or click Installed JREs to search for one.
Note: You must configure a JRE associated with a JDK, because Nexaweb application development and debugging using Tomcat requires a JDK (specifically for JSP compilation).

Configurations: Specifies the name of a pre-set combination of facets to add to this project. Choose the specified default project facet configuration to ensure all available functionality for the server type you selected for this project. Or select another custom facet configuration that you previously defined.

Add project to an EAR: Click the checkbox to add this project to an Enterprise Archive (EAR) file. A default EAR project name appears. Optionally, select another EAR from the drop down list, or click New to locate an EAR file on your local system.

Click Next.
The Select Project Facets dialog appears.

Facets are a new construct in WTP 1.0 to provide a standardized way for you to add and remove functionality from a project. (In previous versions of Eclipse and WTP, each plug-in provider had to provide their own mechanism for managing components of a project.) Previously, Nexaweb provided the add Nexaweb Support functionality to add Nexaweb components to a Java EE application. This functionality has been refactored into a Nexaweb Facet. Now you add Nexaweb Support to a project by adding Nexaweb platform facets to the project. You can add Nexaweb project facets when creating a new project using the New Nexaweb Application wizard, the Eclipse Dynamic Web Project wizard or by editing the properties of an existing project.

Nexaweb applications offer the following facets:

Facet	Description
Dynamic Web Module	Provides application directory structure appropriate for a dynamic web application.
Java	Provides application directory structure for Java components.
Nexaweb accessibility	Provides Java applications with Section 508 compliance.
Nexaweb data binding	Adds the Nexaweb DataFramework plug-in library. The Nexaweb DataFramework provides the ability for you to bind data from external sources in your client UI.
Nexaweb data services	Adds the Nexaweb Data Request plug-in library. The Nexaweb Data Request plug-in provides the ability for your applications to access data from external SQL and web services resources.
Nexaweb data validation	Adds the Nexaweb Validation Framework plug-in library. The Nexaweb Validation plug-in provides the ability for your applications to validate data users-supply through the application UI.
Nexaweb desktop client	Adds the desktop client JAR to the application structure.
Nexaweb platform support	Adds Nexaweb server JARs to the application structure.
Nexaweb web services	Adds the Nexaweb web services plug-in library. The Nexaweb web services plug-in provides the ability for your applications to access data from external web services resources.