Can't use the AWT from a Carbon application
Prior to Mac OS X 10.5, native Carbon applications could not use JNI to access Java code that started the AWT.
Carbon applications can now access the AWT if they follow the guidelines in Tech Note 2147. Specifically, they must start the Java VM on a non-main thread, and must take care to only make Carbon or Cocoa calls on the main thread.
SWT applications that also create AWT windows hang on exit.
An SWT application that created an AWT window would not exit cleanly when the last window was closed. The spinning beach ball appeared and you had to force quit the application.
This problem is now fixed in Mac OS X 10.5. Quitting the application via the application menu or closing all windows now ends the application without any problems.
Last updated: 2007-10-31