Yes, it's the best solution:)
Regards,
Mariusz
On Thu, 2 Apr 2020 at 16:23, Philippe Mouawad
wrote:
> Hello,
> Why not contribute a patch to code of CacheManager ?
>
> Regards
>
> On Thu, Apr 2, 2020 at 4:21 PM Draelants Geert
> wrote:
>
> > I think I’ve found the problem.
> >
> >
Can you check this example: https://github.com/mawasak/custom_jmeter_plugin
?
In jar folder you have compiled file ready to put in lib/ext - you will
have second CacheManager then in Add->Config Element menu (named My
CacheManager)
Source code on github.
JMX is here
Hello,
Why not contribute a patch to code of CacheManager ?
Regards
On Thu, Apr 2, 2020 at 4:21 PM Draelants Geert
wrote:
> I think I’ve found the problem.
>
> HTTPSamplerBase.apples(ConfigTestElement) only accepts the default
> canonical name of CacheManagerGui.
> Because of that my updated
I think I’ve found the problem.
HTTPSamplerBase.apples(ConfigTestElement) only accepts the default canonical
name of CacheManagerGui.
Because of that my updated implementation is never added to the sampler.
Guess I’m gonna have to patch the jar after all.
Regards,
Geert
> Op 2 apr. 2020, om
Hi Mariusz,
The saved .jmx does contain my cache manager with the proper class in @guiclass.
If I enable it and disable the default cache manager then the tests run without
any cache manager at all.
So no, I don’t see that debug line about ‘existing CacheManager superseded’ in
the logs.
Hi,
HttpSampler can only have one CacheManager. Do you see in logs: "Existing
CacheManager {} superseded by {}"? - emitted by setCacheManager.
In code CacheManager it is selected that way as below.
@Override
public void addTestElement(TestElement el) {
if (el instanceof CookieManager) {
Hi,
Does anybody know how I can replace the HTTP cache manager with my own
implementation?
I’m trying to extend the default one with options to (1) consider all
Cache-Control headers (and not just the last one) and (2) process the Pragma
header.*
What I’ve done is extended CacheManager and
