Issue 116993 - Scripting Framework is broken in DEV300m100
Summary: Scripting Framework is broken in DEV300m100
Status: CLOSED DUPLICATE of issue 116991
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: DEV300m100
Hardware: Unknown All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: ab
QA Contact: issues@framework
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2011-02-17 11:03 UTC by Oliver Brinzing
Modified: 2017-05-20 10:01 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 Oliver Brinzing 2011-02-17 11:03:32 UTC 
steps to reproduce:

- download "ScriptDispatch.oxt" from
  http://www.openoffice.org/issues/show_bug.cgi?id=98990

- install extension (shared), for example:
  unopkg add c:\ScriptDispatch.oxt --shared --verbose

- download and open "StartScriptDispatch.odt" from
  http://www.openoffice.org/issues/show_bug.cgi?id=98990

- press button

- nothing happens ...

btw: it worked in m99 but now it's broken :-(

-> regression

set priority to p2 cause this bug will 
prevent me to do any further testing ;-)
Comment 1 ab 2011-02-17 11:24:07 UTC 
STARTED
Comment 2 ab 2011-02-17 13:47:22 UTC 
ab->brinzing:
For me it doesn't work on m99 (wntmsci12.pro) either.
I always get the message:

"A Scripting Framework error occurred while running the Java scrpt
org.test.java.ScriptDispatch.execute

Message: Cannot resolve script location for script =
org.test.java.ScriptDispatch.execute"

Any idea what could go wrong?
Comment 3 Oliver Brinzing 2011-02-17 14:23:12 UTC 
@ab: did you install with option "--shared" ?
Comment 4 ab 2011-02-17 14:39:19 UTC 
@brinzing: I used the Extension Manager UI, but installed "For all",
so this should be the same. To be sure I've just tried via your unopkg
command line and got the same behavior.

Besides this, I *do* see a difference in m100 as there just nothing
happens, not even an error message. It just would be nice to have a
really working version and not to take an error message as success. :-)
Comment 5 Oliver Brinzing 2011-02-17 16:46:57 UTC 
@ab: have you seen:
http://www.openoffice.org/issues/show_bug.cgi?id=116995
maybe same root cause ?

for me (vista 32 bit & jre 1_6_23) m99 is ok (a dialog will be displayed),
but m100 indeed will do absolut nothing...
Comment 6 Frank Schönheit 2011-02-21 08:34:37 UTC 
fs->brinzing: the "nothing happens when you  click the button" is a duplicate of
issue 116991. However, with the fix for this issue, I also get the error (in
m100) which ab describes for m99. So I am not sure whether there is still
another problem.
=> It's at your discretion whether you want to close this issue here as duplicate.
Comment 7 Oliver Brinzing 2011-02-21 12:48:25 UTC 
@fs: i just removed all my extensions from m99 and installed
"ScriptDispatch.oxt" again. it worked like expected - a dialog will
be shown after pressing the button in "StartScriptDispatch.odt".

after unopkg a ".\user\Scripts\shared-extension-desc.xml" should
contain an entry pointing to the extension, e.g.:

<?xml version="1.0" encoding="UTF-8"?>
<unopackages xmlns:unopackages="unopackages.dtd">
    <language value="Java">
        <package
value="vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/3A20.tmp_/ScriptDispatch.oxt/ScriptDispatch/"/>
    </language>
</unopackages>
Comment 8 ab 2011-03-08 14:06:19 UTC 
As the described problem can be explained by 
http://openoffice.org/bugzilla/show_bug.cgi?id=116991
I set this one to duplicate.

*** This issue has been marked as a duplicate of issue 116991 ***