Apache OpenOffice (AOO) Bugzilla – Issue 19974
Q-PCD Programmability-8 (OOoBean) (OOo 1.1.1 parts)
Last modified: 2004-05-18 10:37:06 UTC
Source: Engineering + Marketing Category: Java APIs Product Requirement: Specialized Java IDE GUI Components (JavaBeans) We want to build on top of the native OfficeBean framework more specialized and more customizable beans. This beans should useable from IDEs per drag and drop and so on Customer Need/Problem: It should be possible to use SO/OOo JavaBeans like Swing GUI components in a GUI builder in an IDE. There should be a component for every SO/OOo application (Writer, Calc, Impress, etc.).
adding: OOoBean to summary
see: http://api.openoffice.org/Projects/OOoBean/
added keyword Q-PCD
making this the srx645 parts of the OOoBean
see #i21611 too, which are OOo 2.0 parts
removed keyword Q-PCD again, because this is a non OOo2.0 task (I only want to track OOo2.0 node tasks with the keyword)
The new OOoBean shall be runnable on an OOo 1.1.1. Thus, this issue only coverse the extensions and fixes in OOo itself, including the OOoBean framework (officebean.jar and officebean.so/dll). It does not cover the new OOoBean itself. Changes in OOo are: 1. it is not possible to release the OOo Window Parent from the OOoBean and re-aquire it 2. UNO on the Java side does not keep a dead bridge anymore when OOo crashed or hangs See attachment for testframe.
Created attachment 11979 [details] OOoBean example to be used as a testframe
This issues does not cover that OOo does not crash anymore. It just coverse preparations that the OOoBean can deal with such crashes better.
checked on wntmsci8.pro, lnxigi5.pro and unxsols5.pro
SW->MI: just checked the given office with the new bean on windows. After opening all document types once I pressed the 'release/aquire' and then tried to open all documenttypes again => the office crashes with a 'pure virtual function call'- message.
Created attachment 12015 [details] Test-Frame with loop option
I added a new test frame with a loop option. Under windows OOo might hang after a few tries. But this is a deadlock issue which we cannot address in this release. Andreas Schlüns will try to get it fixed in 1.1.2.
SW->MI: under winxp the crash-guard appears as soon as the bean is closed, afterwards both process hang (java and soffice). To reproduce just start the bean, open a textdocument and then close the bean over the window-closer
This defect is also in SO 7 PP1, with accessiblility tools on. Thus it has nothing to do with this fix. This issue can be closeed. We need to file a new issue against SO7 PP1 to Stephan Schäfer. Even though the fix is dangerous and won't be done in any SO7 PP, we should file this issue, Kay Ramme says.
forwarding to QA
SW: part of cws_sdk10 => fixed
SW: looks good in cws_sdk10 => verified
SW: ok in srx645m27 => closed
Now also part of the 'switched to src680' cws_sdk10 :-)