Home
IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
Java/CORBA Classes
This section documents the Java/CORBA classes.
Java™ Classes Coding Guidelines
Accessing views and folders using Java™
Refreshing a view
Updates (additions, deletions, and changes) to a database are not reflected in an open view until it is refreshed. By default:

IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Domino® Query Language
  Domino Query Language (DQL) is a facility running in Domino core allowing for a terse shorthand syntax for finding documents according to a wide variety of complexity of terms. It leverages existing design elements without the need to write detailed code to access them.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
  - Java™ Classes Coding Guidelines
    - Running a Java™ program
      You can call the Domino® Objects from a Java™ program by importing the lotus.domino package. The program can be coded as an application, a Domino agent, an applet, or a servlet. Local calls access run-time code on the local computer, which must have Domino installed. CORBA-based remote (IIOP) calls access run-time code from a remote Domino server; in this case, the local computer need not have Domino installed. Compilation must be on a computer with Domino Designer installed.
    - Accessing databases
    - Accessing views and folders using Java™
      - Accessing view properties using Java™
        The following methods access the View properties.
      - Locating a view
      - Accessing view columns
      - Working with view entries and navigators
        For navigation and access, a view or folder supports view entries, view entry collections, and view navigators.
      - Refreshing a view
        Updates (additions, deletions, and changes) to a database are not reflected in an open view until it is refreshed. By default:
      - Removing a view
    - Accessing documents in Java™ classes
    - Accessing items in Java™ classes
    - Accessing rich text items in Java™ classes
    - Accessing Domino® sessions
  - Java™ Classes A-Z
- Lotus® Connectors
  Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Refreshing a view

Updates (additions, deletions, and changes) to a database are not reflected in an open view until it is refreshed. By default:

For local operations, a view refreshes automatically when a navigation method touches an updated document. You can suppress automatic refresh by setting isAutoUpdate of View to false.
For remote (IIOP) operations, a view does not refresh automatically. You can enable automatic refresh by setting isAutoUpdate of View to true. However, this turns off caching.

To explicitly refresh the view, call refresh of NotesView. For remote (IIOP) operations, this method invalidates the cache.

It is best to avoid automatically updating the view especially if the view is a base for navigators or entry collections. Automatic updates degrade performance and may invalidate entries in child objects ("Entry not found in index").