On 07/02/06, Mamading Ceesay <[EMAIL PROTECTED]> wrote:
> On Tuesday 07 February 2006 18:52, sebb wrote:
> > >
> > > I considered the Regex Post-Processor, but I think may have had the wrong
> > > idea about where it goes. I suppose I can attach it to the Http Request
> > > that GETs
> >
> > Yes, they should be attached to the GET request.
> > There needs to be one for each string.
> > The matched data are saved in variables (which can be anything).
> >
>
> Ok, I'm clear on that now.
>
> >
> > Functions are used anywhere that variables can be used.
> >
> > e.g. on the Sampler to provide a value for a parameter.
> >
>
> ditto.
>
> > > Now it is:
> > >
> > > javascript:__doPostBack('FooOrgAdministratorLeftMenu1$CreateFooLinkButton
> > >','')
> >
> > Not sure I understand this, but it sounds as though the URL for the
> > postback request has changed. Unless this varies for each postback,
> > this is a one-time fix to the postback sampler.
> >
>
> I'll investigate further. Right now I'm working on the ViewState issue.
>
> > > Since the interface to the engine has changed, blahbot is no longer able
> > > to talk to the blah server. The real problem here is that a hidden form
> > > is filled out using javascript -- the first argument is the "event
> > > target" and needs to be rewritten with ':' for each '$' then saved in the
> > > form.
> >
> > This is where the function comes in - it would translate a$b$c to
> > a.b.c (or whatever).
> >
>
> Understood.
>
> >
> > > Thus, before the captured ViewState can be successfully used, each of
> > > these "+" symbols that are interspersed in the string must be substituted
> > > with "%2B" . This can be reformatted by passing the value obtained by t h
> > > e " LOAD RESPONSE_INFO" command t o a subroutine held in an " Include"
> > > file."
> >
> > This is not the same transformation as $ -> . above, but can be done.
> >
>
> I'm going to try that now.
>
> >
> > > Hope this proves helpful.
> >
> > Ditto.
> >
>
> Thanks a lot, Seb. I think I spent too long pouring over the docs, mailing
> list archives, wiki, demos/examples and stfw. I wasn't seeing the pattern of
> how the relevant JMeter functionality ties together to solve the problem. It
> really helps to discuss this with someone who groks JMeter. I'm a lot
> clearer on things now.
>
> I'll let you know how I progress with this.
>
Thanks.
==
I meant to add previously that it might be worth adding a new element
to JMeter to handle this all automatically.
Perhaps something along the lines of the HTML Link Parser
http://jakarta.apache.org/jmeter/usermanual/component_reference.html#HTML_Link_Parser
This uses information from the previous sample to update the current request.
But it's not yet clear to me if it is possible to make it work in the
general case.
S.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
