DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42660>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42660

           Summary: BeanShell* : add property to specify if "testStarted"
                    etc methods should be called
           Product: JMeter
           Version: 2.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTTP
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Currently, the BeanShellPreProcessor, BeanShellPostProcessor, BeanShellSampler
and BeanShellAssertion all try to call the "testStarted", "testEnded",
"threadStarted", and "threadFinished" beanshell methods.

I think that by default, most people will not implement these methods, and if
they do, it will be in files that they include using the properties in the
jmeter properties file, for example the
beanshell.sampler.init=BeanShellSampler.bshrc property.

To avoid filling the debug log with messages about missing beanshell methods,
and to avoid an exception always being thrown in those four classes whenever
"testStarted", "testEnded", "threadStarted", and "threadFinished" occurs, I
suggest to add another property to the jmeter properties file, to control
whether those four classes should try to call the "testStarted" etc methods.

So I suggest a property a'la beanshell.call_event_methods= true or false, and
false in the default jmeter properties file, and that the four BeanShell*
classes are changed to use that property wisely.

I was also wondering if the four BeanShell* classes in their "init" methods
could figure out which of the "testEnded", "testStarted" etc method are
implemented in the file being sent to the BeanShellInterpreter. Then the classes
could call only those methods it knows are present. But I guess that will be
quite difficult to do, therefore I suggest just using a property.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to