Hi there,
running a macro which gets dispatched as a macro via the OOo 2.4.1 Java
bridge (the Java scripting framework of OOo) will be aborted, if the
Java support (Apache BSF, cf. <http://jakarta.apache.org/bsf>) creates
dynamically an event adapter. Running the same program via URE succeeds!
The Apache BSF employs its own class loader (extending
java.lang.ClassLoader) for caching the dynamically created event adapter
classes (done in
org.apache.bsf.util.event.generator.AdapterClassLoader). Unfortunately,
when dispatched by OOo 2.4.1 as a macro invoking
ClassLoader.defineClass() causes an (uncatchable!) abend. (Running the
same code via URE works as expected.)
What causes this surprising behaviour, and even more important, how can
one come by it! (Support for dynamic languages is dependent on being
able to create Java classes on the fly from time to time.)
---rony
P.S.: Ad Beta 3.0, Dev300m21: currently I am not able to add the
scripting package (same package can be added to 2.4). Were there any
changes to the OOo scripting framework for OOo 3.0 which one needs to
take into account? If so, where would that be documented?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
