You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/01/13 00:21:34 UTC
DO NOT REPLY [Bug 15687] -
Request Parameters Gone Missing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15687>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15687
Request Parameters Gone Missing
jsalvata@atg.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmeter-
| |dev@jakarta.apache.org
Status|NEW |ASSIGNED
------- Additional Comments From jsalvata@atg.com 2003-01-12 23:21 -------
After tracing these arguments through at least 13 different classes, I've found
they end up being merged into an empty collection by the 'value instanceof
Collection' case of AbstractTestElement.mergeIn(TestElement).
This same merging operation is occuring before saving the test plan. I don't
know why, but that's how it is.
The way this merging is implemented guarantees all elements in the result
collection will be unique.
- I don't know in which cases this merging operation is actually used (not only
merging against an empty collection).
- I don't know why it ends up being invoked in those two cases.
- I don't know why HTTP Arguments needs to be TestElement and go through all
this pain.
Anyone knowing please drop me a word.
I'll give it a crack, but will mostly be trial-and-error, I guess...
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>