So, I've been looking into implementing a new style of thread group that supports my recent views regarding the closed system vs open system nature of load testing harnesses. Unfortunately I see that JMeterThread is referenced in;
AbstractThreadGroup public abstract void scheduleThread(JMeterThread thread); JMeterContext private JMeterThread thread; with get and set JMeterThreadMonitor public void threadFinished(JMeterThread thread); StandardJMeterEngine private final Map<JMeterThread, Thread> allThreads; along with a bunch of other places. ThreadGroup expected but nicely confined to only two methods public void scheduleThread(JMeterThread thread) ThreadListener SamplePackage pack = (SamplePackage) threadVars.getObject(JMeterThread.PACKAGE_OBJECT); WhileController res = "false".equalsIgnoreCase(threadVars.get(JMeterThread.LAST_SAMPLE_OK));// $NON-NLS-1$ I would need a JMeterThread like object but it would be some what different than JMeterThread. It's not a subclass as there is stuff in JMeterThread that I wouldn't want. As is often the case when one first tries to extend a framework, there will need to be some refactorings to support my new thread group. So question is, how to proceed? (or to proceed at all) Regards, Kirk
