Sorry, currently there is no way to avoid that. As you already
suspected, printer detection starts at startup in an own thread (as to
not hinder the rest of the startup more than possible).
Kind regards, pl
Philippe Brun (perso) wrote:
Hi,
I'm printing documents from a java program connected to an OO instance
on a remote Linux server. I would like to avoid printer discovery.
In my particular case, a lot of printers are defined on the Linux
server. Printer discovery is expensive and tricky (see issue
http://www.openoffice.org/issues/show_bug.cgi?id=27022 for example).
Moreover, it's useless for me because I know which printer I want to
address, and in my case destination seldom changes for a given instance.
I'm afraid though, that printer discovery takes place when the OO
instance starts on the server, before the remote java program connects
and gets a chance to do anything.
Is there a way to avoid printer discovery and later load (from the API)
the (few) destinations I need on demand.
Thanks for your help.
Regards.
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
