Exception when saving to file in OpenOffice using UNO API (Java bindings)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openoffice.org (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: openoffice.org
I have a blocking problem with OpenOffice in Gutsy. I get the error with the official OpenOffice repository version (2.3.0-1ubuntu5) and with the updated version (2.3.0-1ubuntu5.2) available from http://
I'm using OpenOffice in server mode: I run it on Ubuntu Server 7.10, using xvfb (so I have no gnome desktop). I'm developing a java application that makes use of UNO interface to connect to a live OOo server and do some work on text documents. To achieve this I keep a running OOo instance with this command:
xvfb-run --server-
The problem I get is an exception when I try to save the document to disk:
com.sun.
at com.sun.
at com.sun.
at com.sun.
at com.sun.
at com.sun.
at com.sun.
at com.sun.
at com.sun.
at $Proxy60.
The Java code is this:
public void storeDocCompone
storeUrl = storeUrl.
XStorable xStorable = (XStorable) UnoRuntime.
PropertyValue[] storeProps = new PropertyValue[1];
if (storeUrl.
storeProps[0] = new PropertyValue();
storeProps[
storeProps[
}
xStorable.
xComponent.
}
Please note that:
- it's not a write permission issue: I tried to chmod 777 the destination directory with no success, and the OOo engine is able to create the file with 0 length;
- this whole system (my own application, the OOo headless server installation and configuration) works fine in Ubuntu 6.10 (the OOo version is 2.0.4).
- I tried in Ubuntu Server 7.04, with OOo 2.2 with no success (there is another type of error: while inserting an image into the document, but the exception is aways about UNO calls)
- the same installation works fine with OOo 2.3 on windows xp, without changing a single line of code, so I'm confident it's not an UNO API issue changing from OOo 2.0 (which works on Ubuntu 6.10 and windows xp) to OOo 2.3 (which works only on windows xp).
It's almost a week of hard work that I'm trying to resolve this problem with no hope, so now I'm forced (due to my deadline) to setup my production environment with an Ubuntu Server 6.10 (the only system I was able to make working).
If there's any other info/dump/stack trace I can supply, I would be glad to.
Best regards,
Fabio Da Soghe
Do you still have the issue if you use an upstream build of OOo? (I mean, the binary version that is on their web site for download)? That is what I tried to ask you on the other bug report before you created this one. And yes, thank you for creating the new bug report because this is a different bug.