Issue 512 - loadComponentFromUrl finds no filters
Summary: loadComponentFromUrl finds no filters
Status: CLOSED FIXED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 619
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Mathias_Bauer
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-06 07:39 UTC by schulten
Modified: 2003-12-06 14:52 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 schulten 2001-03-06 07:39:38 UTC 
Loading existing documents through the API from Java and StarBasic doesn't work 
in 619, an exception says the filter doesn't exist although I don't specify a 
filter, rather OO itself selects the filter.

Exception:
FilterFactory::GetByName()
Specified filter not exist!

(BTW: there seems to be a typo in the exception message. Maybe not found would 
be closer to the truth anyway, after all the filter does exist!)


Sample:

dim mProps()
oDesk = createUnoService("com.sun.star.frame.Desktop")
oDoc = oDesk.loadComponentFromUrl("C:\temp\sample.sdw", "_blank", 0, mProps())

Dietrich
Comment 1 Unknown 2001-03-06 15:45:59 UTC 
It might be a filter problem.
Comment 2 schulten 2001-03-07 07:00:42 UTC 
No, the same document loads nicely if I open it with the GUI.
So it seems not to be a filter problem in the sense that the Writer 5 filter 
can't handle this sdw file.
Besides, it doesn't matter if I try to load a calc document. Therefore, to me 
it seems it might be a filter factory problem or the filter factory receives a 
garbled filter name.

Or what did you mean by "filter problem"?

Dietrich
Comment 3 Mathias_Bauer 2001-04-12 12:11:11 UTC 
The problem is that we have indeed a bug in the filter detect service; it does 
not work correctly if no filter name was provided as dispatch argument. If you 
provide a "FilterName" property with any string value ( you could 
use "Dummy" ), the filterdetection should work. We fixed this bug for the 627 
build.
Comment 4 Mathias_Bauer 2003-01-17 13:33:07 UTC 
.