Home
IBM 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 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.
Working with error reporting features
The LotusScript editor in Eclipse (LSEE) provides continuous error reporting and support for using Erl() in a user-defined class.

IBM Domino Designer XPages User Guide
This guide focuses on the aspects of creating applications using XPages technology.
- Product overview
  IBM® Domino® Designer supports applications development for the IBM Domino platform using XPages, forms, views, and other elements such as controls.
- Tutorials
  This section contains tutorials and information about tutorials.
- Administering applications
  IBM® Domino® Designer provides features for administering and managing your work and related files while developing your application projects.
- Designing XPages applications
  IBM® 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.
    - 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.
      - Comparing the Eclipse-based and Notes® LotusScript® editors
        The LotusScript® editor in Eclipse (LSEE) works somewhat differently from the Notes® LotusScript editor.
      - Enabling and disabling the Eclipse-based LotusScript® editor
        This version of the LotusScript® editor in Eclipse (LSEE) works for LotusScript agents, script libraries, and database scripts.
      - Creating a LotusScript library
        You can use the LotusScript editor in Eclipse (LSEE) to create a library of LotusScript scripts.
      - Working with code and comment templates
        The LotusScript editor in Eclipse (LSEE) lets you create and edit templates to be inserted when you create new code elements. The templates can include variables that are replaced with real values when the new code element is created.
      - Editing a full script or script sections
        The LotusScript® editor in Eclipse (LSEE) permits you to work on all sections at once, or one section at a time.
      - Controlling compilation
        Automatic compilation of LotusScript libraries is a preference and is on by default. You can also manually compile all LotusScript in the current application.
      - Working with error reporting features
        The LotusScript editor in Eclipse (LSEE) provides continuous error reporting and support for using Erl() in a user-defined class.
      - Allowing script documents to be saved with errors
        You can optionally save scripts that contain errors. For compilation and execution, the latest script without errors is used. For editing, the latest script is used.
      - Using help in the user interface
        The LotusScript editor in Eclipse (LSEE) provides three kinds of immediate help in the user interface.

Working with error reporting features

The LotusScript editor in Eclipse (LSEE) provides continuous error reporting and support for using Erl() in a user-defined class.

About this task

Continuous error reporting: The editor marks a line containing an error with an X in a red circle. Hovering over the mark displays an error message. On the Objects (Outline) tab, the module and its parents are marked with an X in a red circle.
Erl line number for user-defined class: If an error occurs inside a user-defined class, the line number reported by Erl() is wrong because the class definition is no longer part of Declarations. To go to the correct error line, click Navigate > Go to Erl Line(Ctrl+Alt+L), enter the number returned by Erl(), and click OK.