[api-dev] Re: OOoBean and XDesktop::terminate()

2009-11-03 Thread David Bennett
I'm always getting a DisposedException Error. If I move aBean.stopOOoConnection() down further, after xDesktop.terminate(), no exception arises anymore. But the processes soffice.bin and soffice.exe are still running. Sadly, I haveto use a bash script to do this. This one is configured for

Re: [api-dev] Re: OOoBean

2005-01-20 Thread Simon Mieth
On Wed, 19 Jan 2005 20:40:32 +0100 Jochen Staerk [EMAIL PROTECTED] wrote: Hi, I always thought that adding the class path to your manifest would be sufficient and has the same effect than using the cp-commandline switch but I could be completely mistaken. I thought a MANIFEST like

[api-dev] Re: OOoBean

2005-01-20 Thread Jochen Staerk
Hi Simon, and thanks for your answer and the classloader-sample-code, normally if you have the oo-jars (all from oo-home/program/classes) in your classpath (manifest or CLASSPATH or with the -cp switch) the libraries are found. There is a helüper-class, which load the If you want to deploy your

Re: [api-dev] Re: OOoBean

2005-01-20 Thread Michael Hoennig
Hi Simon, I mean the order can changed by newer releases. The officebean.dll depends on MSVCR70, UWINAPI, sal3, jpipe (this is the order to load it). But this can be changed with OO2.0 or 1.1.x. I have not looked at OO2.0 and I don't know if the new OfficeBean will handle this self, Yes,