> -----Original Message-----
> From: Mike Stover [mailto:[EMAIL PROTECTED]]
> Sent: 11 February 2003 15:26
> To: [EMAIL PROTECTED]
> Subject: RE: Search for GUI classes at startup
> 
> 
> On 11 Feb 2003 at 13:47, BAZLEY, Sebastian wrote:
> 
> > At present, it is possible to add new functions and 
> controllers to JMeter
> > merely by adding a jar to the lib/ext directory.
> > 
> > I'm not sure that I have followed all of the discussions 
> about this, but I
> > think it would be a shame if this facility was lost.
> > 
> > It is useful to be able to test additions without having to rebuild
> > everything. 
> > 
> > It is also useful to be able to distribute add-ons as a jar 
> that can just be
> > added to lib/ext.
> 
> My thoughts exactly.  What I'm thinking of is an ant task 
> that would catalog all the searched 
> classes and create an XML description file.  This would add 
> one task to the developer's list of 
> things to do: 1.drop jar file into /lib/ext. 2. run 'build catalog'
> 
> And, once there's an ant task working, I see no real reason 
> why the same code couldn't be 
> run from a menu option in JMeter.  Thus, if you forgot step 
> #2 and you already started 
> JMeter, then you select "catalog" from the menu and JMeter 
> refreshes itself.

Nice

> 
> But, in the meantime, JMeter's startup time is greatly reduced.  
> 

> > 
> > [BTW: I created a new "local" source tree, which is built into
> > ApacheJMeter_local.jar.
> > If anyone thinks it would be useful, I can tweak the 
> amended version of
> > build.xml for more general use.
> > Or a separate build_local.xml if that is more convenient.]
> > 
> > Thoughts?
> 
> I don't understand what's in the local jar?
> 

at present, just a new function:

At some stage soon we may need to test using hundreds or thousands of pairs
of values, so we've created a function that reads data from a file (cobbled
together from the built-in __counter() function.)

Originally, I just added this in the appropriate place in the Jmeter source
directory and rebuilt JMeter, but 
this is a bit tedious to do for each release - so as an experiment I just
created a jar with the new function in it, put it in lib/ext and voila! -
much easier and quicker (IMO).

The directory structure looks like this:

src/components/org/apache...
src/core/org/apache/...
...
src/local/org/apache/...

with the appropriate additions to build.xml to compile and jar the
directory.


==

If further add-ons are produced (*), we can build them into our local jar,
and distribute them to our testers as needed. [And if the add-on causes
problems, the jar can just be removed.]

(*) we would find a Conditional Controller useful - I think one could
probably be derived from the Interleave Controller ... and then there's a
Stop Test Controller etc.

> -Mike
> 
-- 
Sebastian Bazley <[EMAIL PROTECTED]>
The opinions expressed herein are my own, and are not necessarily endorsed
by my employer ...



_________________________________________________________
This email is confidential and intended solely for the use of the 
individual to whom it is addressed. Any views or opinions presented are 
solely those of the author and do not necessarily represent those of 
SchlumbergerSema.
If you are not the intended recipient, be advised that you have received
this email in error and that any use, dissemination, forwarding, printing, 
or copying of this email is strictly prohibited.

If you have received this email in error please notify the
SchlumbergerSema Helpdesk by telephone on +44 (0) 121 627 5600.
_________________________________________________________


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

Reply via email to