Issue 111536 - wrong handling of extensions in scripting framework
Summary: wrong handling of extensions in scripting framework
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m77
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-11 15:58 UTC by joachim.lingner
Modified: 2013-08-07 15:31 UTC (History)
3 users (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 joachim.lingner 2010-05-11 15:58:34 UTC 
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Scripting/Scripting_Framework

Scripts are identified by an URI (see
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Scripting/Scripting_Framework_URI_Specification).
For example
user:uno_packages/extension_name.oxt
share:uno_packages/extension_name.oxt

Currently OOo tries to find the script exactly as specified. That is, if the URI
contains “shared” then  the extension must be in the shared repository. This is
a bug since the location of extensions is irrelevant. It is also not possible to
use services or xcu files of an extension from a particular repository (shared
or user). Today one has to provide different versions of an extension, for user
and shared extensions, for example, when there are menu items which  execute
script in the extensions.

Example extensions can be found in issue 105169 and issue 98990.
Comment 1 joachim.lingner 2010-05-11 16:00:30 UTC 
.
Comment 2 Oliver Brinzing 2010-05-11 17:14:21 UTC 
.
Comment 3 bmarcelly 2010-05-15 08:20:45 UTC 
Duplicate of Issue 102542 (vote for it !)