summaryrefslogtreecommitdiffstats
path: root/kdejava/koala/org/kde/koala/DOMException.java
blob: d51309cc3ddf6aba0279e24309e94218e75839d0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
//Auto-generated by kalyptus. DO NOT EDIT.
package org.kde.koala;

import org.kde.qt.Qt;
import org.kde.qt.QtSupport;

/**

 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 situation, such as
 out-of-bound errors when using <code>ArrayList</code> .
  Implementations may raise other exceptions under other
 circumstances. For example, implementations may raise an
 implementation-dependent exception if a <code>null</code>
 argument is passed.
  Some languages and object systems do not support the concept of
 exceptions. For such systems, error conditions may be indicated
 using native error reporting mechanisms. For some bindings, for
 example, methods may return error codes similar to those listed in
 the corresponding method descriptions.
 		@short    DOM operations only raise exceptions in &quot;exceptional&quot;  circumstances, i.

*/
public class DOMException implements QtSupport {
	private long _qt;
	private boolean _allocatedInJavaWorld = true;
	protected DOMException(Class dummy){}

	public DOMException(short _code) {
		newDOMException(_code);
	}
	private native void newDOMException(short _code);
	public DOMException(DOMException other) {
		newDOMException(other);
	}
	private native void newDOMException(DOMException other);
}