A Wrapper library consist of a thin layer of code which translates a library's existing interface into a compatible interface. So, no, I dont want a wrapper. Or simple delegates. I want some sort of an active mediator.

Example:

When I create a new Entity object in JVM, the "wrapper" needs to create that entity in the engine by ent_create. But if the entity is modified inside the engine (e.g. through physics, because the lifetime of a particles expired or a level is loaded with sub entities), this has to be reflected in the JVM hierarchy (creating or deleting representative classes).

So it is a wrapper for both sides of the medal, because both sides are active. This mediator passes actively instructions from JVM to the engine (called by the user code) and from the engine to the JVM (invoked or reasoned by the engine). It passes, mhhhh, more like some sort of messages. JVM says: move that entity! Engine says: moved it, but it stuck at XYZ. Mediator says to JVM: adjust that entitiy coordinate to XYZ.

So, this is not just about wrapping the engine function interface. So this is not a wrapper.

@Vent: I think the opposite: most C++/C programmers tend to spoil code ;-) but let us not discuss on the C++/JAVA thing. These are two totally different languages with very different aims and language design choices, so it is everyones right to like one only or both ^^