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] Tue Sep 11 22:41:33 +0000
2007 -------
The problem is not fully resolved, unfortunately! I think there is a subtle
problem untackled yet:
It is true that adding "ScriptProvider.jar" to "uno.ini" will allow to correctly
register the extension and it becomes possible to proceed to create new
libraries, new macros and edit them. (This is also great from the perspective
that I could cater for that in an installation script for 2.3, if it was the
only problem introduced with 2.3 RC2.)
However, when the Rexx macro are run, then BSF raises an error "unsupported
language: rexx" which gets displayed in a popup by OOo.
Tracing this down through the code yields a situation (which has never arisen in
previous version of OOo) where it is not possible anymore to use the class
loader's "getResource("org/apache/bsf/Languages.properties")", as an enumeration
of it will always be empty (this file contains the names of the supported BSF
engines, among them "rexx", of course; it is contained in
"ScriptProviderForooRexx.jar").
Therefore BSF is not able to set up the hashtable of supported BSF engines
anymore!
The reason for this is probably the following statement in BSFManager:
Enumeration e =
Thread.currentThread().getContextClassLoader().getResources("org/apache/bsf/Languages.properties");
As you can see, the current thread's context class loader is retrieved and used
for getting at the property's file resource. The reason for using the thread's
context class loader is that BSF may be dispatched on different threads (e.g. in
server-like use cases), such that it becomes important to use the thread's
context class loader.
I am assuming that in the current implementation of OOo 3.2RC2 something goes
astray at this point, and as a result the returned enumeration object will be
empty.
---
Another observation of which I am not sure whether it got introduced with 3.2
RC2 or existed already in earlier versions: the process' CLASSPATH setting is
not reflected in 'java.classpath' which will be empty! (There are use cases
where the process' CLASSPATH setting resp. the Java classes made accessible via
it, may become quite important.)
---------------------------------------------------------------------
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]
