Thanx to all for this info. The startup option flags are set and it appears that the executable is going quietly out of business since we do not record any hangs during extended operation (the dog that did not bark in the night). There is already a no-helper connection setup with an XBridge listener and general catching of disposed exceptions. JS
-----Original Message----- From: Stephan Bergmann [mailto:[EMAIL PROTECTED] Sent: Friday, March 24, 2006 12:41 AM To: [email protected] Subject: Re: [api-dev] detecting "unrecoverable error" event Stephan Wunderlich wrote: > Hi John, > >> 1.) Most important: is there any way to suppress the dialog so that OO >> just goes away quietly without user intervention. > > > you could start the office with the parameters "-nocrashreport" and > "-norestore" ... e.g. > > soffice.exe -accept=... -norestore -nocrashreport > >> 2.) Convenient: Is there any way to observe the 'unrecoverable error' >> event within our UNO library, so our driver would know to retry the >> text block. > > > as soon as the office is gone this way your library should run into a > "com.sun.star.lang.DisposedException" as soon as the next UNO-call is > send ... this way you know when the office died prematurely. If you set up the UNO connection to the office without the use of any helpers (simple bootstrap, UnoUrlResolver; see the Developer's Guide for details), you have access to the connection's XBridge object, which is an XComponent on which you can listen for a disposed event (which will be sent when the connection is terminated, cleanly or forcfully). -Stephan > Hope that helps > > Regards > > Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
