Patrice Seyed wrote:

thanks for the link, but has anyone done before what I am trying to do with 2.0, i.e. can i get a little more of a lead-in / pointer. Thank you, Patrice

I haven't used OOo this way before but, if it helps, I checked the command line arguments in OOo 2.0.2 Help and they appear valid. As referred in that Help section, I then looked in the 2.0 dev guide (http://api.openoffice.org/docs/DevelopersGuide/DevelopersGuide.xhtml) Section 3.3.1 "UNO Interprocess Connections", under "Starting OpenOffice.org in Listening Mode", and again confirmed that nothing appears to have changed. There is a note at the end of that sub-section re versions prior to OOo 1.1.0 though, which should not apply here as you said you've been running 1.1.x.

On Linux (Fedora Core 3) I ran the following command line:

/opt/openoffice.org2.0/program/soffice "-accept=socket,host=localhost,port=2002;urp;" -headless

I then see:
netstat -a | grep 2002
tcp 0 0 desk.home:2002 *:* LISTEN

Also, "telnet localhost 2002" does not return an error and remains "connected" until I escape from it by typing Ctrl+]. So I assume that soffice is listening and accepting connections. If I type very short random lines of text the connection stays up, but if I type some long random line, I get a "Connection closed by foreign host" message. I then have to kill both the soffice and soffice.bin processes. This again suggests that OOo is accepting connections.

If I have an already running instance of OOo, the command line above returns immediately but appears to switch the running instance into listening mode.

Hope this helps.
Ross


On 6/10/06, G. Roderick Singleton <[EMAIL PROTECTED]> wrote:


On Sat, 2006-06-10 at 02:36 -0400, Patrice Seyed wrote:
> Hi,
>
> I am currently using openoffice 1.1.x as a listener to do conversion of
ppt
> to pdf with the JavaConverter. We have a script that does this with the
> following:
>
> daemon Xvfb :1 -fbdir /tmp &
> daemon ooffice "-accept=socket,host=localhost,port=8100;urp" -display :1
&
>
>
> I have discovered that I can fix conversion problems with certain slides > (that we end up converting to bitmap image files) if i do the conversion
> with openoffice 2.0. I have only verified this by opening the ooffice
gui
> with the ppt and exporting to pdf manually.
>
> I tried doing the same as the above commands with 2.0, however I cannot
get
> the 2.0 process to listen on port 8100 with the commandlines:
>
> daemon Xvfb :1 -fbdir /tmp &
> daemon /opt/openoffice.org2.0/program/soffice
> "-accept=socket,host=localhost,port=8100;urp" -display :1 &
>
> the process starts, but it does not listen on port 8100, and the
conversion
> with JavaConverter is not successful.
>
> for example:
>
> # netstat -nap | grep office
> unix  2      [ ACC ]     STREAM     LISTENING     2117629
> 12892/soffice.bin
> /tmp/OSL_PIPE_0_SingleOfficeIPC_bfa67ba891bd9b76f67a649f29db7e59
> unix  3      [ ]         STREAM     CONNECTED     2117625
12892/soffice.bin
>
> whether I use "soffice" or "soffice.bin" in the command line. Rather
than:
>
> # netstat -nap | grep office
> tcp        0      0 127.0.0.1:8100              0.0.0.0:*
> LISTEN      12933/soffice.bin
> tcp        0      0 127.0.0.1:34288             127.0.0.1:631
> CLOSE_WAIT  12933/soffice.bin
> unix  2      [ ACC ]     STREAM     LISTENING     2118047
> 12933/soffice.bin
> /tmp/OSL_PIPE_0_SingleOfficeIPC_4475afd81af40edd91795492cfa4313
> unix  3      [ ]         STREAM     CONNECTED     2118150
12933/soffice.bin
> unix  3      [ ]         STREAM     CONNECTED     2118045
12933/soffice.bin
>
> for 1.1.x
>
>
>
> Am I going about this correctly? Is there a different mechanism to start > ooffice in 2.0 as a listener/server process. And also, should I be using
a
> different JavaConverter program?
>

I recall seeing that much has changed in this area between 1.1.x and
2.x. Please see http://api.openoffice.org/ as a start for info on this
subject.
--
PLEASE KEEP MESSAGES ON THE LIST.
OpenOffice.org Documentation Co-Lead
http://documentation.openoffice.org/





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

Reply via email to