Nexaweb Application Project Directory Structure

When you create a Nexaweb application project, Nexaweb Studio creates directories and files necessary for your new Nexaweb application.

Error! Reference source not found. shows the project structure for a new Nexaweb Platform Application (Java) as it appears in the Navigator view. The table following Error! Reference source not found. provides descriptions of the directories and to which types of Nexaweb applications they apply appear beside.

$image\img00010.gif$

Figure 7: Project Structure Displayed in Navigator View

Directories	Description	Where Used
.nexawebContent	Contains the files needed for deploying a Nexaweb Application. Nexaweb updates this directory when you perform a full, clean or partial build and the WEB-INF/web.xml file has been changed. Nexaweb Studio controls this directory; you should not modify it. Nexaweb writes of any changes you make to the contents of this directory when you perform a build.	All Nexaweb Application types except: Nexaweb Client Application (Ajax)/Alternate Server
.plugin-lib	Contains any Nexaweb plug-ins that you selected for the project such as data framework or validation framework. If you did not select any Nexaweb plug-ins for this project, this directory does not appear in the project.	Nexaweb Platform Application (Java)
.settings	Contains configuration files for the application. The configuration files nexaweb-client.xml, nexaweb-server.xml and nexaweb-webservices.xml configure application properties for the client, the server or the application web services. You can edit these configuration files using a Studio form or by modifying the XAL source directly.	All Nexaweb Application types.
build	Contains compiled output of content of the source directories.	All Nexaweb Application types.
Studio creates the following source directories under the application's main directory:
src	Contains server-side code that may be accessed by Java Servlets or JSPs. Studio stores builds from this directory in the build\classes output directory.	All Nexaweb Application types.
src-client	Contains client-side code or MCOs. See Managed Client Objects in the Nexaweb Platform Concept Guide.	Nexaweb Platform Application (Java) Nexaweb Client Application (Java)/Alternate Server
src-shared	Contains Java code shared between client and server. Studio stores builds from this directory in the build\shared output directory.	Nexaweb Platform Application (Java) Nexaweb Client Application (Java)/Alternate Server
WebContent	Contains all user defined content used in the application.	All Nexaweb Application types.
XAL (NXML prior to Nexaweb Platform 4.5/Studio 3.0)	Files that the Nexaweb Visual Editor can open appear with the icon $image\img00011.gif$ .	All Nexaweb Application types.

Running A Nexaweb Application

Studio must know which file or URL to use as the start page for the application in order to run the application. By default, the starting page is java-index.xal or ajax-index.xal (or index.nxml prior to Nexaweb Platform 4.5/Studio 3.0). You can specify which file to use as the start page.

To select a file as the start page for an application:

In the Navigator view, right-click on the file to make the start page.
Select Nexaweb > Make Start Page.

In addition, to deploy and run the application, your Studio must have a Web Tools Platform (WTP) server configured. To configure a WTP server if you did not configure one when you installed Studio:

Right click on the Servers view and select New > Server.
The New Server Wizard appears.

Define a new WTP server.
Add projects to this server.
Start the server by selecting Right clicking on the server in the Servers view and choosing "Start".

For more information on completing the New Server Wizard, see the Installation Guide.

Now you can run the application. To run the application, select Run > Nexaweb Application > Run Nexaweb Application or click $image\img00012.gif$ and select Run > Default Nexaweb Client.