Issue 55579 - API: dbaccess.OQueryDesign::com::sun::star::frame::XController
Summary: API: dbaccess.OQueryDesign::com::sun::star::frame::XController
Status: CLOSED FIXED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: chne
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-06 20:15 UTC by chne
Modified: 2013-02-24 21:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description chne 2005-10-06 20:15:04 UTC 
The UNO-API-Trest does not work correct. If getModel() returns NULL an OK-Status
is possible. As result of this the attachModel() failes.
Comment 1 chne 2005-10-07 10:10:25 UTC 
Since OQueryDesign returns NULL this is not a bug in the test. An issue was
found in attachModel(Null) which returns "OK" in src680_m132. If OK is returned
the test checks for equal of the old and the new model. While the new model is
NULL a NullPointerException was thrwon. So this issue will be retarget to
OfficeLater and the new owner is oj.

cn->oj: the method attachModel(NULL) returns OK.
Comment 2 ocke.janssen 2008-08-15 12:36:32 UTC 
Fixed in cws dba31b
Comment 3 ocke.janssen 2008-08-19 12:16:34 UTC 
Please verify. You have also to adjust the test. To open the query design you
have to load it with a ActiveConnection.

attachModel with NULL now return false.
Comment 4 chne 2008-08-29 13:55:27 UTC 
ok in cws => verified
Comment 5 thorsten.ziehm 2010-02-22 15:13:03 UTC 
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  :
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues