svn commit: r1505240 - /jmeter/trunk/xdocs/usermanual/best-practices.xml

[se...@apache.org]

Author: sebb
Date: Sat Jul 20 23:49:12 2013
New Revision: 1505240

URL: http://svn.apache.org/r1505240
Log:
Tweak JSR223 docs

Modified:
    jmeter/trunk/xdocs/usermanual/best-practices.xml

Modified: jmeter/trunk/xdocs/usermanual/best-practices.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/best-practices.xml?rev=1505240&r1=1505239&r2=1505240&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/best-practices.xml (original)
+++ jmeter/trunk/xdocs/usermanual/best-practices.xml Sat Jul 20 23:49:12 2013
@@ -227,7 +227,7 @@ java -jar ../lib/bshclient.jar localhost
 Each BeanShell test element has its own copy of the interpreter (for each thread).
 If the test element is repeatedly called, e.g. within a loop, then the interpreter is retained
 between invocations unless the "Reset bsh.Interpreter before each call" option is selected.
-For intensive load testing, it is recommended to use JSR223 scripting languages which ScriptingEngine implements Compilable, 
+For intensive load testing, it is recommended to use a JSR223 scripting language whose ScriptingEngine implements Compilable, 
 see JSR223 section below for more details.
 </p>
 <p>
@@ -327,9 +327,11 @@ The appropriate property file can be pas
 
 <section name="&sect-num;.11 JSR223 Elements" anchor="jsr223">
 <p>
-For intensive load testing, the recommended scripting language is one which ScriptingEngine implements Compilable interface.
-Groovy is one of them, Beanshell nor Javascript do as of release date of JMeter 2.10, so it is 
-recommended to avoid them for intensive load testing.
+For intensive load testing, the recommended scripting language is one whose ScriptingEngine implements the Compilable interface.
+Groovy is one of them, neither Beanshell nor Javascript do so as of release date of JMeter 2.10, so it is 
+recommended to avoid them for intensive load testing. 
+[Note: Beanshell implements the Compilable interface but it has not been coded - the method just throws an Exception.
+JMeter has an explicit work-round for this bug.]
 
 When using JSR 223 elements, always set caching key to a unique value to ensure the script compilation is cached if underlying language supports it.
 Ensure the script does not use any variable using ${varName} as caching would take only first value of ${varName}. Instead use :