Issue 123421

Summary: OOoBean blocking Writer on closing
Product: App Dev Reporter: schorschlan
Component: sdkAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Normal    
Priority: P2 CC: issues
Version: 4.0.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description schorschlan 2013-10-04 10:24:00 UTC
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.