Issue 109062

@ jsk & jl: Please have a look. Sounds like something  that we should fix asap.

@jsk: When you can reproduce this, then assign it to me.
As for the documentation, it says:

"One can put a couple of localized description files into the extension and
reference them in the description.xml. "

(http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extension_Description)

This may be expressed more clearly.

The problem also exists if the extension-description element of description.xml refers to a non-
existing local file.

To reproduce this problem quickly replace step 3 above by

3b. Add the following lines to description.xml:

	<extension-description>
		<src xlink:href="bla.txt" lang="en" />
	</extension-description>  


Note: The problem is that in my situation an extension with the erroneous description.xml file installs, 
but once it is installed, extension manager does not show up anymore, hence it cannot be unstalled or 
update.

@jl: Thanks for the reference. I now see that the developer documentation states "One can put a couple 
of localized description files into the extension and reference them in the description.xml. ". But when I 
read the documentation of description.xml it was not clear which element has to (!) refer to a local file 
and which element can (!) also refer to a remote file. For example release-notes can refer to a remote 
file. Nevertheless, the problem is not tied to the fact that extension-description referred to a remote 
file.

As for the non-existing file, there is already issue  100744.

The text in the Wiki page Extension_Description is a general description. But
even here, the expression _into_ the extension clearly says that the file cannot
be anywhere in the internet.

The syntax is described in the referenced Wiki page
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements#Element_.2Fdescription.2Fextension-description

There it says :
"xlink:href 	Required. The value is a relative URL to the description file
within the extension."

IMHO this is perfectly clear : 
- the description file is _within_ the extension
- hence an http URL cannot be a relative URL to that file.

@bmarcelly: Thank you. I have overlooked this. The documentation is perfectly clear.

Regarding the issue itself, that extension manager is killed if the xlink:href points to a non existing file, it 
is part of of issue 100744

I see this issue as a bigger problem than the priority of 100744 suggest. If an extension with such a faulty 
description.xml is deployed (e.g. via update), then the average user likely needs to make a clean reinstall 
of OO to recover from this problem. It is not even possible to update the faulty extension to a fixed 
version.

Assign to new default-assignee

Crash at step 6
AOO410m1(Build:9750)  -  Rev. 1562493
Rev.1562493
Win 7