I've created a new package - org.apache.jmeter.testelement.property - and I've begun making the JMeter properties classes. They aren't plugged in yet - doing so will be a big job.
But, I've committed the classes and hope people will look at them and make suggestions. The idea is that the TestElement interface will change and only accept JMeterProperty objects as properties, not Objects. Then, the property objects will be responsible for two main things: 1. A function property will resolve functions when the property is requested, and it will cache values so the retrieval is as fast as possible but also completely dynamic. This will obviate the need to resolve all functions up front for each sample and the need to clone test elements that have functions. 2. Test Elements and properties can be instructed to maintain current state for future retrieval. This means test elements and properties can be modified and added-to and the changes are marked as "temporary" and can be undone later. This will obviate the need to clone samplers for when config objects are "layered onto" them during a test run. I'm hoping this will essentially get rid of all cloning that currently goes on within each JMeterThread. That is, when it's all plugged in and working. -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
