MacOSX Java oddities (was Mac OS X builds of 1.9m93 are available at good-day)

Hi Eric,

> So :
>
>> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../  
>> Libraries
>
> is correct -> try cd  
> /System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../ 
> Libraries
>
> this directory does contains libawt.jniliband all java libs
>
> The next :
> :/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/
>> Home/lib
>
> exists too... Maybe a missing dir ? (and wich one ? )
>
>
> Another test I invite you to do is to start OOo1.9.93 :
>
> 1) with soffice -> web wizard crashes for me, beanshell crashes with  
> pretty message
>
> 2) with directly soffice.bin  -> wizard works for me ?  and beans  
> works not completely (null pointer, but looks better)
>
>
> And for database, it is *exactly* the opposite : works with soffice,  
> not with directly soffice.bin...
>
> If this can help you too...
Thanks. This helped a lot indeed. The problem is that
1) with soffice DYLD_LIBRARY_PATH is correctly set which sets java VM  
to version 1.4.2. So Base and all things requiring Java 1.4 work.  
However with the Java 1.4 Update 1 Apple seems to have introduced the  
oddity that AWT cannot be started in the first thread of an  
application. You need an extra thread to do this. OOo currently does  
not do this. That's why some things are failing.
2) with soffice.bin directly OOo uses java 1.3.1. That's why all things  
requiring 1.4 do not work, but AWT can be started from the first thread  
so other things work.
You can easily verify this by renaming  
/System/Library/Frameworks/JavaVM.framework/Versions/1.3.1 e.g. to  
1.3.1_old which causes OOo to crash when launched with soffice.bin and  
calling e.g. the web wizard.

I'll try to investigate this a little more later today.

Best regards,
Florian