Home
HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
Programming
XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.
Eclipse-based language interfaces
Java™ and LotusScript® have interfaces based on Eclipse as well as the older interfaces based on Notes®.
Eclipse-based Java™ interface
The Java™ interface for agents, libraries, and Web services now opens the Eclipse Java editor. You can switch back and forth between the Eclipse and Notes® editor by selecting or clearing the related Designer editor Preferences.
Adding Java™ archives to the Domino® classpath
You can extend the Domino® classpath, for example, to add third-party JAR files.

HCL Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
- Product overview
  HCL Domino® Designer supports applications development for the HCL Domino platform using XPages, forms, views, and other elements such as controls.
- Tutorials
  This section contains tutorials and information about tutorials.
- Administering applications
  HCL Domino Designer provides features for administering and managing your work and related files while developing your application projects.
- Designing XPages applications
  HCL Domino® Designer provides the means to populate an XPage with controls and other artifacts, and to associate an XPage with data stores.
- Designing composite applications
  You can create composite applications from XPages.
- Programming
  XPages uses JavaScript™ for programming while the forms-based design elements use the formula language, LotusScript®, Java™, and JavaScript.
  - Scripting in XPages
    The scripting contexts are event handlers and formulas. The scripting language is JavaScript™ supplemented by simple actions and expression language (EL).
  - Eclipse-based language interfaces
    Java™ and LotusScript® have interfaces based on Eclipse as well as the older interfaces based on Notes®.
    - Eclipse-based Java™ interface
      The Java™ interface for agents, libraries, and Web services now opens the Eclipse Java editor. You can switch back and forth between the Eclipse and Notes® editor by selecting or clearing the related Designer editor Preferences.
      - Enabling and disabling the Eclipse interface
        The Eclipse interface is enabled by default.
      - Interface description
        The Java™ interface for agents, libraries, and Web services administers the source files and invokes the editor.
      - Copying and pasting files
        You can copy and paste files.
      - Deleting files
        You can delete files.
      - Renaming files
        You can rename files.
      - Compiling and saving
        You can compile and save files.
      - Exporting files
        You can export files.
      - Importing files
        You can import files.
      - Importing script libraries with the Eclipse Java interface
        You can import script libraries.
      - Refactoring
        You can refactor elements.
      - Adding Java™ archives to the Domino® classpath
        You can extend the Domino® classpath, for example, to add third-party JAR files.
      - Debugging Java™ code
        You can debug Java™ code running under control of a Notes® client JVM (Java Virtual Machine).
    - Eclipse-based LotusScript® editor
      The LotusScript® editor in Eclipse (LSEE) is an alternative to the Notes-based LotusScript editor. LSEE takes advantage of the many editing features of Eclipse while retaining most of the Notes® features. You can switch back and forth between the Eclipse and Notes editor by selecting or clearing the related Designer editor Preferences.

Adding Java™ archives to the Domino® classpath

You can extend the Domino® classpath, for example, to add third-party JAR files.

About this task

Do the following:

Procedure

Open notes.ini in a text editor.
Add or modify one or both of the following Notes® variables: JavaUserClasses or JavaUserClassesExt.
After saving the file, restart Domino®.

Example

The format for JavaUserClasses is "JavaUserClasses=" followed by a semicolon-separated list of file specifications. The file specifications can reference JAR files, ZIP files, or directories of CLASS files. The value of the variable is limited to 255 characters. File specifications that exceed the limit are lost. Use JavaUserClassesExt if you think you will exceed the limit. Here is an example:

JavaUserClasses=c:\javautils\jdbcdrivers.jar;c:\javautils\stringlib.jar

The format for JavaUserClassesExt is "JavaUserClassesExt=" followed a comma-separated list of tags. The notes.ini file must contain additional entries in the format "tag=" followed by a file specification. Here is an example:

JavaUserClassesExt=jdbc,string  
jdbc=c:\javautils\jdbcdrivers.jar  
string=c:\javautils\stringlib.jar