Ramon F Herrera wrote:
Perhaps my concern (see Subject line) could be addressed in
a simpler way. I was mostly satisfied with the simplest and
most common (at least in tutorial stuff) way of starting OOo:
Bootstrap.bootstrap();
But, after a lot of experimentation I have concluded that
you cannot possibly disconnect from OOo when it is started in
the above bootstrap() fashion. If there were a way to disconnect,
I would be satisfied, until a more general UDDI is added.
Yes, life cycle control of soffice is a known problem (there probably
are even issues for it in the issue database). After
Bootstrap.bootstrap() has connected to soffice, soffice can later find
out when that connection has been closed (because your application has
terminated) and could in principle then terminate itself (i.e.,
terminate itself once no more clients are there). Just not
implemented... ;)
-Stephan
So the question becomes: is there any way to disconnect programmatically
from a session started by Bootstrap.bootstrap()?
There is some Close and VetoableClose or whatever stuff, maybe somebody
from the framework who knows the details can kick in.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
