Issue 11726 - cannot assign a binding to a script deployed to a document
Summary: cannot assign a binding to a script deployed to a document
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: 644
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: OOo 2.0
Assignee: noel.power
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-21 18:34 UTC by robert.kinsella
Modified: 2003-03-13 11:10 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 robert.kinsella 2003-02-21 18:34:29 UTC 
SFrameworkInstall.jar.21.02.2003, StarOffice build 644 m (OO.org 644 not yet
available for test), Solaris 9 and Windows 2000.

Create a starwriter document e.g. testbind.sxw. Save and close the document.
Using NetBeans deploy a beanshell script e.g. bean1 to testbind.sxw.
Restart StarOffice, open testbind.sxw, select tools, scripting add on's, assign
script to Menu. Select location document, language beanshell.

BUG--> the saved script to the document should be made available for binding it
is not.

The only way around this bug is to 
1.deploy the bean1 script to the user area
2. deploy the script to the document
3. create a binding to the script in the user area
4. remove the script from user area (not the binding just the script)
5. open the test document (testbind.sxw)
6.  selecing location document, language beanshell, create a new binding within
the document.
7. this results in an error as the new binding is also displayed on an empty
document
8. the new binding is now working in the testbind.sxw document.
Comment 1 robert.kinsella 2003-02-21 18:41:35 UTC 
changing target milestone.

Note the workaround for binding to a document only works on Solaris,
it does not work on windows.
Comment 2 Unknown 2003-02-24 07:36:56 UTC 
Assign to Noel to fix
Comment 3 noel.power 2003-02-24 10:23:47 UTC 
Started
Comment 4 robert.kinsella 2003-02-24 17:33:58 UTC 
installed SFrameworkInstall.jar.24.02.2003. There is a functional
improvement with this jar in that when the user selects to assign a
script from a document it lists the script in the assign script to
menu dialog, script window.
After selecting file, and entering a name in the assign script to new
menu dialog box, select new and ok an error is reported

On solaris "Error, Unable to write to StarOffice configuration file
<office-install>/user/config/soffice.cfg/writermenubar.xml
Action: PLease make sure you have write access to this file"

On windows
"ScriptNameResolverImpl:resolverURIfromstorageID:cannot.get/XScriptInfoAccess"
Comment 5 robert.kinsella 2003-02-24 18:20:04 UTC 
Note when user selects cancel on the error dialog which pops up for
windows the same error message as has been previously noted on Solaris
is seen.

Then something very strange happens, exit StarOffice and restart it,
repeat the steps to bind a menu setting to a document script - and....
it works. Howver there exists one further problem. The binding which
was created on the menu  e.g. File-bean1, is displayed on all writer
documents, even new documents - I would presume that the binding
should only be visible for the document for which it was created.
Comment 6 robert.kinsella 2003-02-25 12:38:42 UTC 
Tested on clean install of SFrameworkINstall.jar.24.02.2003, verified
working on both Solaris and windows, marking issue as fixed.
Comment 7 robert.kinsella 2003-02-25 12:53:41 UTC 
marking issue as verified
Comment 8 michael.bemmer 2003-03-13 11:10: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.