<aside>
I don't think (I hope!) one would need to change the JMX file handling much,
if at all.
For user parameters, I was thinking of allowing say ${=jmeter.prop} to be
replaced by the value of jmeter.prop. This would not change the JMX syntax.
The Thread Group currently requires the JMX property to be an integer
string; it might not be much of a change to allow other strings, but I've
not looked at it.
I agree that the JMX format is awkard to maintain manually, and relatively
verbose. Changes to the format definitely need to wait until after 1.9. I'm
sure Jython would be fine, but perhaps we should also consider Java
BeanShell? [I want to experiment with that anyway.]
</aside>
I agree that getting 1.9 out of the door is more important than
enhancements. Likewise user-friendliness, i.e. updated documentation and
test-scripts. I'll try to contribute to that effort.
Sebastian
P.S. Thanks for all your hard-work committing various changes, and the
helpful e-mails here and in JMeter User.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 11 June 2003 18:05
To: JMeter Developers List
Subject: Re: Command-line and logging enhancements - followup
These sound like interesting ideas, but it also sounds like you might be
recreating a lot of elements in the .jmx file on the command line. I
suspect
the endpoint of such enhancements will be a JMeter scripting language that
is
easy to look at, manually edit, and less verbose than XML.
Still, it's definitely worth thinking about - my own personal preference is
to
bundle Jython with JMeter so that people can script in python and control
JMeter with it (I like this because it's so easy to do).
However, I'm trying really hard to get 1.9 out the door. There is some
urgency
for me to get it out as soon as possible in good shape, and I think it's
best for
the enhancements to hold off until after that. In the meantime, much
documentation needs to be written/upgraded, including javadocs. I would
greatly appreciate that kind of help from anyone out there (particularly if
you've
written a component - always nice to include the docs for it!).
-Mike
On 11 Jun 2003 at 17:10, BAZLEY, Sebastian wrote:
>
> [snip]
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20575
>
> Command-line and logging enhancements
>
> ------- Additional Comments From [EMAIL PROTECTED] 2003-06-11 14:46
> -------
> I like this one!
>
> [snip]
>
> Thanks! Hope it proves useful (the -P flag has already been useful to me).
>
> With a few(?) code tweaks, JMeter properties could perhaps be used to
define
> various thread group parameters, such as number of threads and loop
count.
> This would be useful for our testing (at present we tend to use Perl to
hack
> the values in the JMX file).
>
> One could then use the same script to run various scenarios.
>
> Equally, it would be nice to be able to change some of the user parameters
> on the command line, e.g. hostname or password perhaps.
>
> I'm happy to create some patches, unless anyone else is already working
on
> this?
>
> --
> The opinions expressed herein are my own, and are not necessarily
endorsed
> by my employer ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
