On 06/09/07, Ronan Klyne <[EMAIL PROTECTED]> wrote: > sebb wrote: > > On 06/09/07, Ronan Klyne <[EMAIL PROTECTED]> wrote: > >>> By the way, BeanShell tends to leak more memory if the script is on > >>> the screen; using a file seems better. Best is probably to define the > >>> script as a method in a startup file and then invoke from a file or > >>> the screen. > >>> > >> I'm trying to do this, but I can't make it work. > >> I am using a Simple Config Element to set both > >> 'beanshell.preprocessor.init' and 'beanshell.postprocessor.init' to be > >> 'BC\funcs.bsh'. I then try to invoke one of these functions from the > >> screen, and get an error in jmeter.log saying "Typed variable > >> declaration" (And quoting a bit of the code). > >> Should it be working when I do this? > > > > No, you need to set them as properties before starting JMeter, e.g. in > > jmeter.properties (or user.properties). > > Wouldn't that make these functions accessible to all of my test plans?
Yes. If you use different directories for the different projects, try adding a user.properties file to each (I think that overrides the one in bin, but check first). > I'd prefer to keep the project specific stuff out of other projects if > possible - is this possible? Yes: * local user.properties (if that works) * use an additional properties file (-q) * define the properties on the command-line (-J) > # r > > -- > Ronan Klyne > Business Collaborator Developer > Tel: +44 (0)870 163 2555 > [EMAIL PROTECTED] > www.groupbc.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
