https://issues.apache.org/ooo/show_bug.cgi?id=123421

            Bug ID: 123421
        Issue Type: DEFECT
           Summary: OOoBean blocking Writer on closing
           Product: App Dev
           Version: 4.0.0
          Hardware: PC
                OS: Windows XP
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sdk
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

I have a Java application which uses the OOoBean internally. When the
application starts it also tries to open office.exe.

[code]
String path = System.getenv("UNO_PATH");
path = path.replace('\\', '/');
String commandLine = "\"" + path + "/soffice\" -nodefault -norestore
-nocrashreport -nolockcheck -nologo -accept=" + interProcCommunicationString +
";urp;StarOffice.ServiceManager";
Runtime.getRuntime().exec(commandLine);
[/code]
I can open and close  the Writer as usual parallel to the Java  application. In
the next step the Java application opens the Writer internally and creates and
shows an empty document. The OOoBean connects whith the office.exe.

oBean.startOOoConnection("uno:" + interProcCommunicationString +
";urp;StarOffice.ServiceManager");

I can open and close  the Writer as usual parallel to the Java  application
here, too.
But if I now close the part of the program using the empty office document I
can never get the Writer, which is running at the same time, to close. I can
get it to open, but not to close.
It doesn´t matter if I call stopOOoConnection or terminate desktop.

this.oBean.getOOoDesktop().terminate();
this.oBean.stopOOoConnection();

>From my understanding of Open Office it must have something to do with
XTerminateListener and TeminateVetoException.
I haven´t figured out how it should work. Especially because it works when the 
OOoBean hasn´t done anything yet and when it is showing the empty Office
document.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.

Reply via email to