I am encountering the following known issue in IDL v8.2.3: 43850 Java Export Bridge: Error if Non-Drawable Object Instantiated First If you create a Java application that incorporates both drawable and non-drawable IDL wrapper objects, instantiating the non-drawable object before the drawable object will cause a runtime error that looks something like: Exception in thread "main" java.lang.UnsatisfiedLinkError: Native Library path_to_your_AWT_library already loaded in another classloader Workaround: Create an instance of a drawable wrapper object first. This will initialize the Java export bridge correctly, allowing both drawable and non-drawable wrapper objects to execute properly. I discovered that this is a known issue as of IDL v7 by searching through release notes, but there is no indication that it is still a known issue, nor that it has been fixed in more recent versions. Does this issue still exist? In my case, I am encountering the issue by instantiating an IDL object and then subsequently creating another JFrame outside of IDL. Creating the JFrame first works ok, but due to the nature of the application, either object may need to be created first and it would be convenient if there were a way to work around this programmatically.