Normal Java doesn't expect exactly matching signature. It expects that you
don't throw anything else than was originally declared. It is perfectly ok
to NOT throw anything at all, which is what Yeti declares for all methods
it generates. Since JVM is inherently unchecked (Java checked exceptions
are checked at compile time only), it's ok at runtime.
So essentially Yeti is lying to Java compiler, which breaks the safety of
Java checked exceptions, but it shouldn't make integrating Java and Yeti
code harder.