Silvio Moioli - 2008-07-26

Hello,
    I have an incompatibility problem in my app - hope that someone has ideas here. The problem is quite complicated:

1) in Mac OS X, every UI element must be managed from the first (0) thread (this is an OS limitation AFAIK);
2) Java is an exception to rule 1) since Apple's AWT and Swing implementations "multiplex" automatically relevant calls to thread 0;
3) SWT is an exception to rule 2) since Eclipse Foundation's implementation doesn't do the multiplexing. To get around this Apple added a JVM switch (-XstartOnFirstThread) that allocates JVM's first thread to thread 0 at the OS level. That way you can happily use SWT;
4) Sadly, if you turn on -XstartOnFirstThread, fobs4jmf deadlocks (no matter if you use SWT, AWT, Swing or none at all).

Probably something in fobs or fobs4jmf doesn't like the JVM allocating threads that way. Note that this happens even if I use jmf from a secondary (non 0) thread.

Summary: fobs4jmf doesn't work with -XstartOnFirstThread, so it cannot be used with SWT in the same app in Mac OS X.

See: http://74.125.39.104/search?q=cache:oIGIUcql8AEJ:www.telscenter.org/confluence/pages/viewpage.action%3FpageId%3D8349+SWT_AWT&hl=en&ct=clnk&cd=6

Does anybody have ideas on how this could be solved/worked around?

Thanks in advance,

Silvio Moioli