To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=81445
------- Additional comments from [EMAIL PROTECTED] Sun Sep 16 22:23:58 +0000 2007 ------- @sb: Thank you for your answer. I went back and studied the ClassLoader and CLASSPATH infos again. - Re getContextClassLoader(): BSF is a Java library, which is written such that it can be deployed in any kind of environments (it got originally created to allow JSPs to employ scripting languages in a very easy manner). The BSF library should be deployable in any dispatch-kind environment (possibly supposed to use different configurations), even where it is a custom to set the thread's context ClassLoader accordingly. (AFAICT, the Thread's contextClassLoader has never been meant as a hack, e.g. cf. deployment techniques in J2EE.) The new behaviour of OOo 2.3 in loading Java components uses a customized ClassLoader (com.sun.star.lib.unoloader.UnoClassLoader, having Java's java.net.URLClassLoader as its parent), but OOo does not set the respective thread's contextClassLoader to its customized one. Therefore by default the Thread uses the System ClassLoader a.k.a. Application ClassLoader (AppClassLoader). The problem now: BSF retrieves the Thread's context ClassLoader (expected to be set by the invoking method), but it did not get set by OOo (to the used UNOClassLoader). The BSF needed configuration cannot be retrieved as a result. The question is, given that you judge context ClassLoaders as problematic ("hack"), whether one could count on it to be set by OOo in the next version nevertheless? - Re CLASSPATH: the CLASSPATH environment variable, if set, is honored by the System (Application) ClassLoader. Some "java binaries" allow for overriding the CLASSPATH environment variable by a switch like "-cp" resp. "-classpath". Only in this case would a set CLASSPATH environment variable not be honored (but replaced). If OOo does not pass on the CLASSPATH environment variable's value at all, such that the Java System/Application ClassLoader cannot honor it, without any other expliticly defined CLASSPATH overrides, then I think it is an error and should be corrected for the OOo Java support as quickly as possible. [Also, how about defining an extension directory for OOo?] --------------------------------------------------------------------- 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]