startOFMLDebugging
void startOFMLDebugging(
string sessionId,
string[] debugModes,
int traceLevel,
int detailLevel,
string outputDevice,
string[] debugClasses
)
debugModes
A list of zero or more of the following: Semantics (semantic errors), Collision (detected collisions), TableErr (errors reported by oiTable()), ExplWarn (explicit warnings), Func (function trace), Func2 (utility function trace), Warn (warnings), Info (further information), Time (time (in seconds) used by function), Time2 (start and end time of function), and Progress (reports calls to xOiSendProgressEvent2App()).
traceLevel
Function trace level (depth), must be non-negative
detailLevel
Detail level must be greater than zero
outputDevice
Either log or file (log if empty or missing).
If set to log, messages appear as NOTICE in application log file and, if configured, in session log (but note that the default size of the session log is probably insufficient to hold all the debug messages generated by operations like insertOFMLArticle or setPropertyValue).
If set to file, messages are appended to file debug.out in the current working directory (which should be the same directory as the current directory of EAIWS when it was started). If the file can’t be opened for writing, messages are written to stderr, potentially interfering with the communication between FApi-Shell and EAIWS. Thus a client should use file if and only if it knows that FApi-Shells have permission to create a file in their current directory, or to write to the file if it already exists (and that the client has permission to read the file).
Furthermore, for EAIWS to accept file the application property egr.eai.gf.cobra.enable_file_io must be set to true.
debugClasses
The list of class names for which to produce debug messages. Unless the list is empty debug messages are limited to classes whose name is given in this list.
Class names must adhere to the syntax for OFML identifiers.