1 files changed, 40 insertions, 0 deletions
diff --git a/tdejava/koala/org/trinitydesktop/koala/DOMException.java b/tdejava/koala/org/trinitydesktop/koala/DOMException.java
new file mode 100644
index 00000000..9fd20f6e
--- /dev/null
+++ b/tdejava/koala/org/trinitydesktop/koala/DOMException.java
@@ -0,0 +1,40 @@
+//Auto-generated by kalyptus. DO NOT EDIT.
+package org.trinitydesktop.koala;
+
+import org.trinitydesktop.qt.Qt;
+import org.trinitydesktop.qt.QtSupport;
+
+/**
+
+ DOM operations only raise exceptions in &quot;exceptional&quot;
+ 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);
+}