Issue 11892 - interactive beanshell scripting does not work on 'saved' documents
Summary: interactive beanshell scripting does not work on 'saved' documents
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: 644
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: duncan.foster
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-27 17:00 UTC by robert.kinsella
Modified: 2003-03-13 11:12 UTC (History)
1 user (show)

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


Attachments
trace of soffice not launching interactive beanshell scripting (6.20 KB, patch)
2003-02-27 17:01 UTC, robert.kinsella
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description robert.kinsella 2003-02-27 17:00:14 UTC
SFrameworkInstall.jar.27.02.2003, StarOffice 644 build m5, Solaris and Linux (rh8)

On a new document select tools, scripting add on's, interactive beanshell
scripting,  - an interactive beanshell scripting dialog box is launched.

Set security to always (under tools, options security) and open a previously
saved text document. Select interactive beanshell scripting again, this time
nothing happens. The user would expect that interactive beanshell scripting
should work for documents, and also follow the security settings under tools,
options.
Comment 1 robert.kinsella 2003-02-27 17:01:41 UTC
Created attachment 4929 [details]
trace of soffice not launching interactive beanshell scripting
Comment 2 Unknown 2003-02-28 10:50:29 UTC
Assign to Noel to Fix - Noel looks like we have an example of the
security issue already raised. If you look for a non fully qualified
URI and there are no permissions set for doc you will fail and come
back out the whole way instead of continuing to search in user and share.
Resolve in ScriptRuntimeMgrImpl needs fixed to handle this.
Comment 3 Unknown 2003-03-04 07:50:39 UTC
Should be fixed as part of security mods
Comment 4 duncan.foster 2003-03-05 11:10:52 UTC
Fixed, checkPermissions now thrtows an AccessControlException right
the way up to the ScriptNameResolverImpl which handles it appropriately.
Comment 5 duncan.foster 2003-03-05 11:37:34 UTC
Dialogs relating to document permissions will still be displayed. This
should be fixed as part of issue 12060
Comment 6 robert.kinsella 2003-03-10 13:04:37 UTC
verified fixed in ed-0.2
Comment 7 michael.bemmer 2003-03-13 11:12:10 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.