Hi all,
Berin has convinced me that using the Avalon-Excalibur framework in
JMeter would be helpful. I'd like to know if everyone is agreeable to
letting me rework JMeter's structure to do this.
to be specific, it will require changing the interfaces (such as
JMeterComponentModel and ModelSupported, Saveable, etc). The way new
components would be written would change (the idea is to make is easier and
more consistent).
I think the benefits of this would be:
1. Simpler and more consistent process to create new components
2. Remove dependence on Swing in non-gui classes
3. Better design resulting in easier to manage and less buggy code
4. Possibly more flexibility in the types of components JMeter handles
(right now there's a rigid and somewhat arbitrary categorization of
components as "timers", "listeners", "config elements", "logic controllers",
and "generative controllers". "Assertions" and "Modifiers" were new
elements that have been tacked on. Using Avalon, the organization of
existing and new elements would be much more flexible.
Only fair to list what I see are the disadvantages:
1. Lot's of work that will delay many new features everyone wants
(cut/copy/paste, better reports/visualizers, etc).
2. Work that may interfere with what you are working on currently
And, the risks:
1. May introduce complexity for relatively little gain. Berin probably
doesn't see this as a risk, cause he is comfortable with Avalon. It looks
pretty good to me, but I see the potential that the new abstractions may
confuse things, and not produce as much benefit as I think. Obviously, I've
decided this risk is small, but others may not think so.
Perhaps a branch could be made for this work. I'd rather avoid that though,
if possible.
Any thoughts?
-Mike
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
