I'm going to work on eliminating as much of cloning in JMeter as possible. For my first bit, I'm thinking of adding some new methods to the TestElement interface to allow one to tell a TestElement to preserve it's current state so that it can be recovered at some future point. Thus, when samplers get "layered" with config elements, we won't have to clone the samplers. Instead, the sampler will be made a "Running Version", and the layering can be undone after the sample by calling "recoverRunningVersion". No cloning, just some temporary objects to hold the config elements.
Most of it can be implemented in AbstractTestElement, though several TestElements will need their own implementation. Basically, I'm finding that TestElements that hold collections have to be more clever about it. However, I'm also planning on implementing a TestElementProperty interface and making various property objects, ala Oliver's branch, and in the end, the properties will hopefully take on much of the burden of these complications. Any suggestions or questions are welcome. -- 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]
