Classpath
The classpath is set by mounting directories and JARs to the project's
Filesystems collection. By default, some of the JARs are mounted when
Forte starts, and do not appear in the Filesystems tab.
When using the Kelp Application Wizard, additional JARs may be added to
the mounted Filesystems if they are required to build the default
configuration.
Project directory
The project directory is where Kelp will look for the default input,
output and source directories, or their equivalents. As NetBeans does not
create a tangible project directory the way JBuilder does, the user
will have to provide this directory. By default, the Project directory is
assumed to be the first directory added to the project (not to be
confused with the first mounted directory). This default can be overridden
via the XMLC "Project Directory" property
(Tools/Options/Uncategorized/XMLC Compiler).
Source directory
Kelp uses the source directory as the parent for all generated
packages. The source directory defaults to <project_dir>/src, but this can be
overridden by adjusting the "Source Directory" XMLC property.
Output directory
Kelp for Forte does not have an output directory, per se. The output
directory is the same as the source directory, and this is where the
class files should be generated on compilation.
Deploy root
The deployment root directory can be set through the Kelp deployer
property sheet (Tools/Options/Uncategorized/Kelp Deployment).
Run options
When deploying your app, if you have chosen to run your application
from the IDE, a StartServer.java file will be generated. In this case, a
pre-configured external executor should be attached to the StartServer
file, so you can right-click the node and select Execute from the
context menu.
Setting up a project for use with the Kelp ApplicationWizard
If the Kelp Application Wizard is used to jumpstart your development
effort, we recommend the following project setup:
1. Create the project directory.
2. In NetBeans, select Project|Project Manager|New from the main menu.
3. In the Create New Project dialog, enter a name for your project.
Kelp does not use this project name internally, so there are no
naming restrictions.
4. Once the project is created, mount your project directory.
5. Select the Project tab in the Explorer window.
6. Right-click on the project root and select Add Existing from the
context menu.
7. Select your project directory and click the "OK" button.
You are now ready to generate a new application. Select File|Kelp
Application Wizard to launch the Kelp Application Wizard.
Once the Wizard is finished, folow the instruction in the readme file.
File is automaticly show on screen.
See "Using the Kelp Application Wizard" for more details.
Notes/Troubleshouting:
- Disable module HTTP Server, and all depending modules
(Tools/Options/IDE Configuration/System/Modules/Web/HTTP Server).
This will be done automaticly on Windows only, after first start.
- After abnormal NetBeans shoutdown (fatal exception, system crash...)
it is required to delete file
<netbeans_user_dir>/system/modules/org-enhydra-kelp-forte.xml.
- Execution of StartServer may fail if classpath specifed in Kelp
Executor startup line is too long. Try to move required jar somewhere closer
to the begining of the path. You can view and change Kelp Executor
startup line under Tool/Options/Debugging and Execututing/Execution
Types/Kelp Executor, property runOption.