Issue 108078 - "General Error" pop-up when I use the writer's default template in the extension
Summary: "General Error" pop-up when I use the writer's default template in the extension
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 3.2 RC1
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
Keywords: regression
Depends on:
Blocks: 111112
  Show dependency tree
Reported: 2010-01-05 09:27 UTC by kamataki
Modified: 2017-05-20 11:42 UTC (History)
9 users (show)

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

WriterTemplateForJa.oxt (13.52 KB, application/vnd.openofficeorg.extension)
2010-01-05 09:29 UTC, kamataki
no flags Details
WriterTemplateExtensionError01.png (231.69 KB, image/png)
2010-01-05 09:30 UTC, kamataki
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kamataki 2010-01-05 09:27:23 UTC
I developed some extensions. Among them, an extension to set a default template
came to display an error dialogue at the time of start of from
3.2. I did not watch this problem to 3.1.1. Will this problem be
a bug caused by 3.2?

Because even DefaultSettingsForJapanese.oxt[*] which Japanese many users use
occurs, this problem is serious. But this problem occurs only in Writer and does
not occur in Calc, Impress, Draw. In addition, there is not the hindrance when
We use a default template of Writer.

Reproduce scenario:
1. Please install WriterTemplateForJa.oxt which I attached.
2. Click "Text Document" at "Welcome to" window.
3. Like WriterTemplateExtensionError01.png which I attached, a "General Error"

Comment 1 kamataki 2010-01-05 09:29:03 UTC
作成された添付 (id=66987)
Comment 2 kamataki 2010-01-05 09:30:01 UTC
作成された添付 (id=66988)
Comment 3 kamataki 2010-01-05 11:01:54 UTC
As for WriterTemplateForJa.oxt, language setting works in "English(USA)".
Comment 4 michael.ruess 2010-01-05 14:32:46 UTC
MRU->OS: please have a look. When the attached extension is installed, creating
a new Writer document will give a "General Error" - but a Writer document will
be opened though. 
The error message did not rise in OOo 3.1.1.
Comment 5 kamataki 2010-01-06 01:55:04 UTC
Thanks, mru.

I wish this issue is fixed with 3.2.1 if possible.
Comment 6 Oliver Specht 2010-01-07 14:38:08 UTC
While creating the new document a lot of assertions from urlobj.cxx are printed
due to the use of a template URL starting with "". The
ErrorHandler is caused by an exception caught in swxml.cxx with the message:
"invalid attempt to assign an empty interface of type". 
My debugger refused to show mew the source of the exception. 
The assertions and the exception are probably related. 

Comment 7 carsten.driesner 2010-01-07 15:28:39 UTC
cd->mav: Do you have an idea what could be the reason for this error message.
Comment 8 mikhail.voytenko 2010-01-07 15:42:56 UTC
It looks like somebody tries to get interface
from an object using UNO_QUERY_THROW. It is hard to say without debugging which
exactly implementation does it.
Comment 9 carsten.driesner 2010-08-06 15:33:54 UTC
cd->mav: Please have a look.
Comment 10 mikhail.voytenko 2010-08-09 13:59:47 UTC
The problem is that the expand: URL is not a hierarchical URL per definition and
thus is not supported by service. As result
some new functionality that uses the mentioned service does not work.

The non-hierarchical expand protocol is actually not really useful in OOo
implementation. And thus it would be nice to exchange it with a new protocol.
Unfortunately the support for the new protocol that is intended to exchange it
is still not at the state that it could be integrated in OOo 3.3. Thus the
problem has to be workarounded in the new implementation for now by expanding
the URL explicitly.

mav->mst: Sending to you as discussed.
Comment 11 2010-08-11 11:37:44 UTC
now i have a simple workaround:
expand the URI manually before using it.

this is ugly but until the extension framework switches to using for %origin% it is an acceptable workaround.
Comment 12 2010-08-12 14:26:37 UTC
fixed in cws sw33bf08
Comment 13 2010-08-19 11:09:31 UTC
please verify
Comment 14 2010-08-19 13:44:25 UTC
CCed: mst
Comment 15 stefan.baltzer 2010-08-23 11:44:15 UTC
Verified in CWS sw33bf08.