On 5 July 2013 16:24, Danny Lade <[email protected]> wrote: >> -----Ursprüngliche Nachricht----- >> Von: sebb [mailto:[email protected]] >> Gesendet: Freitag, 5. Juli 2013 16:29 >> An: [email protected] >> Betreff: Re: Groovy >> >> > I'm not sure how could you know the code about JSR223TestElement is >> > implementing the support for "script compilation caching", so here comes >> some short code: >> > >> > processFileOrScript() >> > // Hack as in bsh-2.0b5.jar BshScriptEngine implements Compilable >> > but >> throws new Error >> > boolean supportsCompilable = scriptEngine instanceof Compilable >> > && >> > !(scriptEngine.getClass().getName().equals("bsh.engine.BshScriptEngine >> > ")); >> > >> > Because the JavaScriptEngine is based on the BshScriptEngine the "script >> compilation caching" >> > isn't available for Java, but it is available for groovy. >> >> Which JavaScriptEngine? >> > There is no physical implementation, but if you use the "JSR223 Sampler" it > provides the language "Java". This is made via the BshScriptEngineFactory > which provides the information it also "speaks" Java.
OK, I see. > (see > https://code.google.com/p/beanshell2/source/browse/trunk/src/bsh/BshScriptEngineFactory.java?r=94) > However, the "script compilation caching" does not work for Java (provided by > BshScriptEngine). > > Besides that, it seems they removed the Java support in newer versions (see > same link, but newest version). You should consider that if you think about > using "bsh-2.1b5.jar" in the future. No, we cannot use beanshell2 from that source as it is GPL. However the original beanshell code is hopefully coming to Apache. >> > I'm not saying "you must install groovy" , I just want to be sure >> > having a scripting engine with "script compilation caching" working (or >> > without >> any synchronization during runtime). >> >> What I am saying is that there is no need to include Groovy in the JMeter >> binary >> release. >> It works just as well if it is downloaded separately. >> >> And if the BSH Compilable bug can be fixed, users could then use BeanShell. >> > It's the same on me, I just want to point out the "script compilation > caching" with BeanShell. > All I did was to suggest possible solutions (IMO), the decision is all yours. > > Greetings Danny >
