On 09/09/08 09:47, ashok _ wrote:
On Tue, Sep 9, 2008 at 9:54 AM, Stephan Bergmann
<[EMAIL PROTECTED]> wrote:
Most probably that Java exception is caused by the soffice process crashing,
so you would need to have an eye on the soffice process (e.g., attach with a
debugger; OOo's crash handling might prevent a core being generated for a
process that would otherwise generate one).  And yes, multithreaded access
to OOo is known to be, erm, adventurous.



Thanks for the feedback... Does that mean if i have a java Swing UNO
client, the only way to safely access the XComponent handler is to run
all the document processing via the XComponent handle on the main
event dispatch thread (EDT ? ) rather than a background thread... ? Is
there a better way to do this....because running all the document
processing on the EDT slows everything down... ?

You could move all communication with OOo to a single thread (which need not necessarily be the EDT, but could also be a dedicated thread you create), or use mutexes to avoid multiple threads communicating with OOo simultaneously.

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to