To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68285
User as changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |WONTFIX
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Sep 14 23:15:10 -0700
2006 -------
Sorry - but I dont mix something here. The problems more in detail:
What do you mean, which of the following URLs is right and which is wrong ?
"file:///f:/temp/test.odt"
"http://www.any.org/test.odt";
"vnd.sun.star.expand://1904678/test.odt"
"vfs://Desktop/test.odt"
"blubber://myfiles/test.odt"
ANY Of these URL's can be right or wrong. Why ?
Do you know the UCB. It's our internal used service to access contents in a
generic way. And these UCB provides a "plugin" concept. You can register
several
further UNO components bound to an URL schema.
The most well known URL schemas are implemented inside OOo itself. "vnd.sun.
star.expand:/" is a special schema to access contents inside UNO-Packages; "vfs:
/" was designed to bind gnome VFS contents to OOo and "blubber:/" does not
exists currently - but it can be written might be by you .-)
On the other side I cant ask the UCB how many and which type of contents it
supports. Because there is a special fetaure inside gnome. So the "vfs:/"
content
provider is also registered for the schema "*:/". What does it mean ? Gnome
knows
the same plugin concept. You can extends gnome vfs by plugins so it can support
several URL schemas. And because OOo does not know which URL schemas are
supported by gnome ... OOo must forward all unknown URLs to Gnome.
Another problem: Inside OOo (means the current design of the UCB) there is no
function like "File::exists()". Because some programmer decided, that such
function cant work in a multithreaded and shared environment (which is IMO
right).
The only way to know if a file exists or not is to open it and handle errors.
But the
UCB can not provide the right errors here ... because he also not know
(sometimes) if the URL was wrong (because not supported by any plugin ... think
about "*:/") or if the requested file does not exists.
Another (small) problem:
Do you know the URL schemas "private:factory/*" or "component.db:/" or
"bibliography:/" ? Such URL's cant be used to create a stream. They are
supported
by special FrameLoader implementations, which create the content
programmaticly. These schemas has to be handled manually to know if a failed
stream creation was realy an error or not.
I know - it's not perfect ... But if your bug with upper case URL's will be
fixed
everything will work as aspected. And such "false positive
IllegalArgumentExceptions" wont occure any longer. The only way to reproduce
this bug then will be: using of realy realy unsupported URL schemas or (!)
providing
an illegal content as e.g. "file:///f:/temp/test.pdf" for loading. The same
exception
will occure in case the file exists ... but its format type is unknown or not
supported
for loading (because PDF can be exported by OOo only).
Sorry again: but the decission about changing the behaviour was made some
months before and we cant redefine it every day. The signature of the API
method
isnt perfect ... the internal designs are also not perfect (They are flexible
but not
perfect). But now I can guarantee (more then before) that in case you dont got
an
exception the return value will be valid and can be used.
Please dont reopen this task. The decision about this behaviour is final. Only
a new
implementation XComponentLoader2:loadComponentFromURL2() can help to solve
(some) problems. But currently there is no decision about that.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
