DOM operations only raise exceptions in "exceptional" circumstances, i.e., when an operation is impossible to perform (either for logical reasons, because data is lost, or because the implementation has become unstable). In general, DOM methods return specific error values in ordinary processing situations, such as out-of-bound errors when using NodeList.

Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if a null argument is passed when null was not expected.

index or size is negative or greater than allowed value

the specified range of text does not fit into a DOMString (not used)

a node is inserted somewhere it doesn't belong

a node is used in a different document than the one that created it

an invalid character is specified (not used)

data is specified for a node which does not support data

an attempt is made to modify an object where modifications are not allowed

an attempt was made to reference a node in a context where it does not exist

the implementation does not support the type of object requested

an attempt is made to add an attribute that is already in use elsewhere

a parameter or an operation is not supported by the underlying object

an invalid or illegal string is specified

an attempt is made to modify the type of the underlying object

an attempt is made to create or change an object in a way which is incorrect with regard to namespaces

an attempt is made to use an object that is not, or is no longer, usable

Creates a DOMException with the given error code.

Creates a DOMException by copying another one.

Destroys the DOMException.

Returns the name of the exception class.

See also: Poco::XML::XMLException::className()

Creates an exact copy of the exception.

Returns the DOM exception code.

Returns a static string describing the exception.

See also: Poco::XML::XMLException::name()

(Re)Throws the exception.

See also: Poco::XML::XMLException::rethrow()