Nope. The jar executes, determines local platform, and (if Windows) downloads the JNI DLL. Then and only then does it execute the
java code backed by the JNI DLL.
(Obviously my jar is running with all possible privileges at this point).
Packaging the DLL inside the jar - never thought of this. It would add unnecessary download time on unix boxes, but that might not be a deal-breaker... any problems to look for here?