Specifications

Note:
This function returns the localized message derived from the operation
attribute and the relevant message arguments using the algorithm
used for log messages.
List classes: ConnectionList, JobList
Due to implementation limitations Switch is unable to return an array of Connection, Job or
Occurrence instances. Instead, it returns a helper object of the corresponding list class, that is,
ConnectionList, JobList or OccurrenceList respectively.
These helper classes offer the following functions to access the items in the list.
Returns the number of items in the list (may be zero).
getCount( ) : Number
Returns the item in the list at the specified
(zero-based) index. If the index is out of range, the
function returns null.
getItem( index : Number) : Connection
or Job or Occurrence
This is a read-only property (rather than a function)
that contains the value returned by getCount().
length : Number
Returns the same value as getItem(index).
at( index : Number) : Connection or Job
or Occurrence
18.8 Metadata module
Map class
A Map object (that is, an instance of the Map class) holds a set of mappings from an XML
namespace prefix to a full namespace URI. These mappings are used for resolving namespace
prefixes in XML element and attribute names. See also XPath expressions, XMP location paths
and the Node class in the XML module.
Constructing Map objects
There is no direct constructor for Map objects. Instead the Dataset class (in the Metadata module)
and the Document class (in the XML module) offer functions to obtain a new Map object. Each
class offers two distinct functions:
createEmptyMap( ) returns a new empty prefix map object.
createDefaultMap( ) returns a new prefix map object that already contains all mappings that
occur in the XML document associated with the receiving object
In case the script developer can easily determine the set of prefix mappings used by a script, the
preferred mechanism is to add that list of prefix mappings to a newly obtained empty prefix
map. In reality however this is not always practical. For example, a query expression (with
prefixes) might be provided by a user at run-time and the script developer may wish to avoid
exposing the complexity involving namespaces to the user.
476
Enfocus Switch 10