To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47888
------- Additional comments from [EMAIL PROTECTED] Fri Sep 2 04:34:23 -0700 2005 ------- In order to avoid the main thread patch I tried to use Java 1.3.1, instead of 1.4. If I understood things correctly the AWT threading issue should not apply there, right ? I added the path of the 1.3.1 installation to the directory search list in module jvmfwk (the g_arSearchPaths[] in util.cxx). Building the whole module with debug shows a lot of useful debugging messages, so I could verify that the 1.3.1 VM was actually started when I clicked on Tools->Options->Java (note, you have to copy the dynlibs, a softlink results in config files not being found at runtime). However, and this clearly contradicts what I initially thought, the very same message about AWT being started from the wrong thread appeared and the 1.3.1 VM was not considered useful. Moreover, this exception appeared regardless if I applied the svmain patch or not! Patrick, do you have an idea why the 1.3.1 VM cannot be successfully loaded ? Do you think this approach would be useful at all ? All OOo Java code should be 1.3.1 compliant, so we could, at least for now, avoid the patch and limit ourself to the 1.3.1 VM. As NeoOffice/J runs successfully with 1.3 there must be a way... --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
