Hi Chris,
I'm going to tell you the same thing I've told others: you can always become a
committer anytime by asking and being voted for. This isn't a firesale :-)
But, it's good to go through those first few contributions by working with a current
committer and getting him to committ your patch. That way, we will feel more
comfortable with you, and you will probably know better if you really want to work
with JMeter.
I have further, more specific comments below:
On 12 Dec 2002 at 11:55, [EMAIL PROTECTED] wrote:
> Hello.
>
> [snip]
>
> Company:
> I work for Westfield Group. We are a medium size insurance company in
> Westfield Center, Ohio, just south of Cleveland. We currently have been
> using LoadRunner to test our performance of our web application, but have
> been keeping our eyes out for something else. I first noticed JMeter a few
> releases ago, but it couldn't handle our application. I re-looked at it
> when it came out at version 1.8, and it shows to have a lot of penitential.
> My manager was really excited to see if I could get it to work with our
> application and I have been really impressed that it was handling our 129
> HTTP Requests and doing it with multiple threads. To get it to fully work,
> I had to make some changes to the code. Since my changes I find it easier
> than running LoadRunner.
Woohoo! Score one for the good guys :-) I'm always glad to hear good stories
like this.
>
>
> My Changes:
> I had to make some changes to the modifiers. The problem I had with the
> current modifiers was that it only looked for attributes in the previous
> HTTP Request and only filtered out the first occurrence. These values
> could change each and every run for us. So to make that work I created two
> modifiers. The first modifier filters out the session arguments for every
> occurrence and stores that information. I patterned this class off of
> URLRewritingModifier and this works for the whole thread. I created
> another modifier, which I extended URLRewritingModifier. I overrode the
> 'modify' method to get one of the stored values that was filtered and call
> URLRewritingModifier's 'modify' method to finish the rewriting. I had to
> change the 'modify' method to 'protected' to make that work. I ran into a
> problem with all the modifiers when I was doing them remotely. I found out
> that the Perl5Compiler was 'null' on the remote side. So I created another
> method that is called 'getCompiler'. This will check if it is 'null' and
> if so create a compiler and then return the value. Also some one said that
> the modifiers didn't work in 1.7 in the non-gui mode, but it works for me
> in 1.8. I have just finished up and will be sending my patch for
> consideration. I didn't say anything earlier, because I do not like
> submitting until I am ready.
Some of the problems with non-gui from 1.7.x to 1.8 have been improved. Also,
from the sound of it, you could probably benefit from learning about functions in
JMeter. I suspect your modifier is giving you some of the same capabilities that
the "__regexFunction" provides. Look it up in the component reference page if
you haven't already.
>
>
> Little Background of me:
> I have been programming in the business world for nine years, but have been
> playing with computer languages since I was eight. Don't hold it against
> me, but I was in the Microsoft world doing C, C++, and VB for my company
> and then we changed to Java, and have been doing that for the last four
> years. One thing I really like about this world is the open source.
That's all that matters.
--
Michael Stover
[EMAIL PROTECTED]
Yahoo IM: mstover_ya
ICQ: 152975688
AIM: mstover777
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
