Return-Path: Mailing-List: contact bsf-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list bsf-dev@jakarta.apache.org Received: (qmail 73335 invoked from network); 13 Jun 2003 06:44:16 -0000 Received: from out001pub.verizon.net (HELO out001.verizon.net) (206.46.170.140) by daedalus.apache.org with SMTP; 13 Jun 2003 06:44:16 -0000 Received: from outgoing.verizon.net ([4.62.118.88]) by out001.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030613064424.MXRM12592.out001.verizon.net@outgoing.verizon.net> for ; Fri, 13 Jun 2003 01:44:24 -0500 Received: (from critter@localhost) by outgoing.verizon.net (8.11.6/8.11.6) id h5D6iOP29770 for bsf-dev@jakarta.apache.org; Fri, 13 Jun 2003 02:44:24 -0400 Date: Fri, 13 Jun 2003 02:44:24 -0400 From: "Victor J. Orlikowski" To: bsf-dev@jakarta.apache.org Subject: Re: Public availability of the global scope variable Message-ID: <20030613024424.K29597@critterling.garfield.home> Mail-Followup-To: bsf-dev@jakarta.apache.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from ire0@us.ibm.com on Thu, May 08, 2003 at 09:04:35AM -0500 X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [4.62.118.88] at Fri, 13 Jun 2003 01:44:24 -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, May 08, 2003 at 09:04:35AM -0500, Ivan Eisen wrote: > I have and application where Rhino JavaScript routines are executed > repeatedly.�� I have compiled them and cached the executable;� however,� I > had to modify the com\ibm\bsf\engines\javascript\JavaScriptEngine.java > routine to get� the private variable Scriptable global.� I need a way to > get the global scope so that I can get to declared beans that in our > JavaScript routines.�� Are you planning to make the global scope variable > available in a future release?� If so when is that release scheduled. > Apologies again for the late reply, Ivan. It had not been the intent to provide access to the global scope via the Scriptable variable global. I am curious as to why you need access to this variable; since you have declared the beans to BSF, and modified them via Javascript, you should still be able to access them via the calling Java code. I'm afraid I need a little more information, to understand your requirements. Victor -- Victor J. Orlikowski | The Wall is Down, But the Threat Remains! ================================================================== orlikowski@apache.org | vjo@dulug.duke.edu | vjo@us.ibm.com