https://bz.apache.org/bugzilla/show_bug.cgi?id=65116
--- Comment #2 from eR@SeR <nale...@gmail.com> --- Created attachment 37729 --> https://bz.apache.org/bugzilla/attachment.cgi?id=37729&action=edit pop up messages Hi, > a) It is about merging functionality from external plug-ins into JMeter We can discuss it on dev list, as you suggested. Thorough testing should be done for sure. > At the moment the best we could do, would be to display a warning, that a > function was not found. > For such a warning, we would have to decide, where to display it - log > message or display a dialog? As I said, for other plugins we have pop-up error message shown. So, yes both log message and dialog display should be done. Example images for the Dummy sampler are in the attachment. You can follow the same pattern as shown in the images. > I think, that this can't be changed easily. The way JMeter currently works, > is that it tries to find a function by the name inside the ${...} constructs. > JMeter doesn't know or care, where the function was defined (plug-in or > built-in). So, we can't tell a user function X should be provided by plug-in > Y. Yes, that's right. That is the job of jmeter-plugins-manager-1.6.jar file, I guess. IDK how it works, since it detects properly which jar file to download if the plugin is not installed. If pop-up error message is implemented, probably the change should be done on JMeter plugins side as well - to point to the corresponding jar file download. The most important thing here is that JMeter notifies user that functions, that are not part of the core are detected and that the loaded jmx file won't work as expected. -- You are receiving this mail because: You are the assignee for the bug.
