Am 28. November 2016 20:18:22 MEZ, schrieb "Epp, Jeremiah W (Contractor)"
<[email protected]>:
>Whoops, forgot to address this after my machine was rebooted by a power
>outage and then work got in the way. Sorry about that.
>
>> -----Original Message-----
>> From: Felix Schumacher [mailto:[email protected]]
>> Sent: Tuesday, November 15, 2016 2:51 PM
>> To: [email protected]
>> Subject: Re: How should no-op setter methods be filed in Bugzilla?
>>
>> Am 14.11.2016 um 20:20 schrieb Epp, Jeremiah W (Contractor):
>>>> -----Original Message-----
>>>> From: Felix Schumacher [mailto:[email protected]]
>>>>
>>>> I have attached a test case that models this, with the only
>downside,
>>>> that it works with current trunk.
>>>
>>> Thank you, though I have to admit I'm not sure how to correctly run
>that.
>>> Unfortunately, nor do I really have time to get deep in this problem
>right
>>> now. The example was really just to show the _class_ of problem
>I've had to
>>> work around. There have been a slew of these.
>>
>> Is this class of problems, those classes, that use instance variables
>for
>> state instead of jmeter-properties?
>
>Beg your pardon? I was saying its representative of a category of
>similar
>examples that only differ in the class and method name.
The class you mentioned uses an instance variable instead of using
this.setProperty(...), so I thought that this might be your problem and wanted
to ask, of the other examples you found, have the same property (that is, not
using setProperty).
>
>>> Let's try this: if you were going to export those postProcessors in
>your
>>> test to a JMX file on the disk, what would the code look like?
>>
>> Well, if I remember correctly, you are using JMeter in quite some
>> interesting ways, that are not the usual ones. So it may very well
>be,
>> that you find interesting behaviour.
>
>I'd say it's a moderately interesting application at most. I've only
>had to
>extend one class; 99% of what I have is pretty obvious use of the APIs.
>
>> The only way I save elements is to let JMeter save them and I haven't
>> looked to deeply into that, yet.
>
>I've tried. XStream is kind of obtuse, and I'm still trying to figure
>out
>the point where the data structure is lowered to a HashTree that
>SaveService
>can work with. If I knew that, I might be able to _fix_ it.
I would love to hear more about this, when you have something to report here.
Regards,
Felix
>
>Regards,
>Wyatt
>
>Confidentiality Notice: This electronic message transmission, including
>any attachment(s), may contain confidential, proprietary, or privileged
>information from Chemical Abstracts Service ("CAS"), a division of the
>American Chemical Society ("ACS"). If you have received this
>transmission in error, be advised that any disclosure, copying,
>distribution, or use of the contents of this information is strictly
>prohibited. Please destroy all copies of the message and contact the
>sender immediately by either replying to this message or calling
>614-447-3600.
