since Swing is a presentational thing only and JNI is mainly a way to call routines written in other languages, the short answer is yes. The long answer is that using a *LOT* of JNI will quickly cause all but the bravest soul to run far, far away. You'd be highly recommended to clearly define one single java utility class that acts as a mediator between the two sides of the JNI world, mainly to cut down on getting the stubs generated and compiled into your native app and keep the "hair tearing" bits isolated.