Mailing-List: contact bsf-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Bean Scripting Framework developers" <bsf-dev@jakarta.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 74.125.46.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FxehML9jtWc5nDjnrZOejQhz8G0Fy11Rtq4t7GYl2dRggSa1yzca4Ncp3MfyFR7B3698zMetR/BvSPy4EsVExUxl4Dn+klLbManmtWWxMaY87mm885pVunyu0XVWzO6nQexDwEHYlAr3V/D4a+wHwGePCTrXtQaJz5e+oMyOVn4=
Message-ID: <25aac9fc0805200348v22339c38g940f1a5104d00946@mail.gmail.com>
Date: Tue, 20 May 2008 11:48:22 +0100
From: sebb <sebbaz@gmail.com>
To: "Bean Scripting Framework developers" <bsf-dev@jakarta.apache.org>
Subject: Re: How about a static "getRegisteredEngines()" ? ( Re: JEXL engine
In-Reply-To: <48327D39.3060201@wu-wien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <ce1f2ea80805141354i784ccf35w8ba542ad4fb93a07@mail.gmail.com>
	 <482B653E.6040509@wu-wien.ac.at>
	 <ce1f2ea80805141849t465d8294mccaca64d27da835d@mail.gmail.com>
	 <4831C81D.4080804@wu-wien.ac.at>
	 <ce1f2ea80805191153l50eeee5cs713698fca5bafb9b@mail.gmail.com>
	 <4831D75B.1000107@wu-wien.ac.at>
	 <ce1f2ea80805191300p67e7cb93taf944935418f8892@mail.gmail.com>
	 <25aac9fc0805191436j79cd2470r927522488f40fc76@mail.gmail.com>
	 <48327D39.3060201@wu-wien.ac.at>

On 20/05/2008, Rony G. Flatscher <Rony.Flatscher@wu-wien.ac.at> wrote:
> Hi Sebb,
>
>
> >
> > >  Sebb - Would it help JMeter to have this? If so, can you please add ;-)
> > >
> > >
> >
> > I can't at present think of a reason why JMeter would need the version
> > at run-time, because we bundle a known version.
> >
> > But it might well be useful for other applications, e.g. web applications.
> >
> >
>  From experience such metadata is not needed every day (like true
> mutliple-inheritance etc.), but if you run into a need for it then the
> availability appears to be just God sent!
>
>
> > However, it would be nice for JMeter if BSF made it easy to retrieve
> > the list of registered languages ;-)
> >
> >
>  That's an interesting suggestion. Currently, BSFManager employs a HashTable
> of registered engines (langName->classNameOfEngine) which could be made
> available via a static "getRegisteredEngines()" accessor method. Would that
> help solve your use case?
>

Yes - at present JMeter has to read the properties file and keep track
of others it may add itself (only Jexl so far) so they can be
displayed in the GUI.

I'll do a JIRA for the enhancement.

>  Would anyone object to add that static method to BSFManager?
>
>  Any other suggestions/ideas/requests?
>  [I would like to work a bit on the code this coming weekend, mainly to
> incorporate the Jira issues/requests, but then it would be also possible to
> add the one or other useful functionality.]
>
>  ---rony
>
>  P.S.: Personally, I would like to incorporate ant's nice class that
> incorporates all JSR-223/Java6/BSF3 scripting engines into BSF2.4, cf.
> <https://svn.apache.org/repos/asf/incubator/tuscany/sandbox/ant/container.script/src/main/java/org/apache/tuscany/container/script/jsr223/JSR223BSFEngine.java>
> using the org.apache.bsf package name.
>
>  P.P.S.: In addition, I have been thinking of another idea which would allow
> JSR-223/Java6/BSF3 to employ BSF2.4 scripting languages, distributed with
> BSF2.4.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: bsf-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: bsf-dev-help@jakarta.apache.org