The OAL will add to the logs by calling the message(Level, string) methods. The application controls how messages are logged and which ones are logged.

Use this class in two steps:

1. Implement Listener . There you can specify where to send the log (for example, by calling System.out.println or by stuffing a database). You can also filter out the ones you don't want by checking the moduleName and level in Listener.logMessage(System.DateTime, Level, string, System.Exception) .
2. Specify in your application which levels of logging you want by calling addListener(Level, Listener) for each kind you want like this:

    DOF.Log.addListener(DOF.Log.Level.DEBUG, myLogListener);
               

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

ERROR

Wherever you might write code to guard a user callback like this:

Copy
threadpool.submit(new Runnable() {
public void run() {
try {
userCallback();
} catch (Exception t) {
//Handle uncaught exception
}
}
});

Do this instead:

Copy
threadpool.submit(new DOFListenerInvoker(core, "MyListenerInterface.userCallback") {
public void invoke() {
userCallback();
}
});

Of course, you can always use it synchronously like this:

Copy
new DOFListenerInvoker(core, "MyListenerInterface.userCallback") {
public void invoke() {
userCallback();
}
}.run();

See tryCallbackThrow() and tryCallbackErrorException() for additional usages.

Must be created with a Builder . This class is immutable once built. Any changes will need to be made using the Builder.Builder(DOFQuery) constructor.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

These configurations are immutable once built, and so the builder allows them to be created (and modified) up until they are built.

The values returned by the State reflect the values at a time in the past.

Requestors initiate interest requests with DOFSystem.beginInterest(DOFObjectID, DOFInterestLevel) . Providers react to ACTIVATE-level interest requests using this listener.