To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=93964
------- Additional comments from j...@openoffice.org Mon Oct 19 10:41:21 +0000 2009 ------- The problem is that "soffice extension.oxt" fails with the message "Java implementation loader couldn't be created". Which is possible caused be the Java VM in the office process and the one in the uno process which use the same debug parameters. The problem is described here http://wiki.services.openoffice.org/wiki/Extensions_trouble_shooting A possible solution would be to use the debug setting of the java framework. One can use bootstrap parameters, such as -env:UNO_JAVA_JFW_PARAMETER_1=-Xdebug -env:UNO_JAVA_JFW_PARAMETER_2=-Xrunjdwp:transport=dt_socket,server=y,address=8100 which are currently only usable in "Direct mode". See jvmfwk/inc/jvmfwk/framework.h The java framework could be adapted that the bootstrap parameter overrides the user settings. Then one needs a bootstrap variable for the extension manager, which is used to pass particular bootstrap variables on to the uno child process. For example, soffice is started like this: soffice -env:EXTENSION_MGR_UNO_PARAMS=UNO_JAVA_JFW_PARAMETER_1=-Xdebug The extension manager would then pass UNO_JAVA_JFW_PARAMETER_1=-Xdebug to the uno process. --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
