Exception catch problem

Hi, our team use kilim based on kilim1.0. Here, we has a problem about Exception-catch . The problem we can reprodue by code:

package kilim.examples;

import kilim.Mailbox;
import kilim.Pausable;
import kilim.Task;

public class IllegalArException extends Task {
	public static void main(String[] args) {
		new IllegalArException().start();
	}

	public void execute() throws Pausable {
		int i = 2;
		try {
			new Mailbox<String>().get(1000);// RPC
			throw new DolphinRunException();
		} catch (DolphinRunException ex) {
			System.out.println("DolphinRunException:" + i);
		} catch (Exception ex) {
			System.out.println("Exception:" + i);
		}
	}

}

class DolphinRunException extends RuntimeException {
	
}

expect result:

DolphinRunException:2

but we get the result:

Exception:2

Thanks first.

[walkerzhao]

Thanks, We will try kilim 2.0 in our services. I have moved the commit to our team inner kilim version, it works fine now.

[nqzero]

i released org.db4j:kilim:2.0.0-15 to maven central with the fix above. i included a java 7 version using the jdk7 classifier, fixed a bug in the java 7 build, and added some docs on using kilim 2.0 with java 7. i have not yet decided if i’m going to automate the jdk7-classifier releases

https://github.com/nqzero/kilim/tree/f96867ed67797b670f87503a1ff5cc1a658cd287

kilim 2.0 should be compatible with most 1.0 code (the public api for kilim has always been poorly defined, so it’s possible that you’ve used portions of kilim that we didn’t consider public). if you’re having trouble migrating to kilim 2.0, i’m happy to work with you to figure out why and add missing functionality back into 2.0 or document the correct workaround. if you’re interested, create an issue. kilim 2.0 is still pre-release so it’s easy to make changes at this point. it will be harder once an official 2.0 release is made

i’m closing this issue. if you still see problems with exception handling, please reopen it