Hi,
John Sisson wrote:
Hello
We have a Java gui client that manages a pool of oo documents (xp +
oo.1.1..3) and executes oo-Basic macros on them via a UNO XDispatch
interface. We also have Java robotic processes that need to do the same.
While we can serialize attempts to execute macros in a
Hi,
it is a known fact that OOo has several multithreading problems. Most
of them reveal when using OOo API via remote UNO. Every single
multithreading problem can be considered a bug, but fixing all of them
is a rather complex task (due to the size and complexity of OOo code).
However, we're
Hello
We have a Java gui client that manages a pool of oo documents (xp +
oo.1.1..3) and executes oo-Basic macros on them via a UNO XDispatch
interface. We also have Java robotic processes that need to do the same.
While we can serialize attempts to execute macros in a single client (or
robotic)
