Hi Vincent, On Wed, Aug 13, 2008 at 5:00 PM, Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi Wang, > > On Aug 13, 2008, at 10:53 AM, Wang Ning wrote: > >> Hi, >> >> I just finish start up a openoffice server in java code using >> Process oooProcess = Runtime.getRuntime().exec(oooCommand); >> The process's name is "soffice". But later the process change its name >> to "soffice.bin"(or the old "soffice" process end and start a new >> process named "soffice.bin". I' >> m not sure). I found that I can't use oooProcess.destroy() to close >> the "soffice.bin" process. >> >> How to close it by java programming? > > To be honest, I'm not sure how useful it is to start it automatically. I just want user only install the office converter plugin and openoffice and don't need care about how to start up the openoffice server. > > My take is that we could: > * Install a public OO server somewhere that users can use directly IMO, this way have many problem. 1) The remote openoffice server connection is not stable. 2) If many user connect to the public server, how to control the use of the public server resource. I mean if someone request to the public server too often, the public server may crash. > * bundle an OO server in one of our distributions. In this case it > could be started in the same way as we start xwiki, i.e. using a shell > script I think this way is great. So I will stop the automatic-star-up from the code. > > WDYT? > > Thanks > -Vincent > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs >
-- Sincerely, Wang Ning _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
