Ramon F Herrera wrote:
Stephan Bergmann wrote:
Ramon F Herrera wrote:
(5) connection = xConnector.connect(con); <-- finally!, there is IPC
here
That creates a connection from OOo to OOo. Probably not what you want.
If that is the case, how come every single client example (except the
ultrasimplistic, those that don't care about disconnecting) found in the
SDK and elsewhere uses the
connection = xConnector.connect(con); // pipe or socket
statement? See, for instance, "Connection Aware *Client*"? (1)
The subtlety to note is where the xConnector is implemented (determined
by the ComponentContext it is instantiated at)---at the client or server
side.
My contention is that in order to make a connection-aware program, the
first requirement is to make a socket/pipe IPC or else you will not be
able to kill the session/bridge programmatically.
No, the problem is not to get rid of the bridge (it vanishes all by
itself once no longer used), the problem is a defined life cycle of the
soffice process (i.e., that the soffice process terminates once there
are no more clients)---as I already wrote in another mail.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
