Hey all, I'm investigating how much of a deal it would be to extend Jmeter to handle the specifics of GWT-RPC (but specifically not deRPC, nor RequestFactory) such that Jmeter can be used for performance/stress/load testing capabilities of Jmeter.
So far, it seems that I could take these as a starting point reference because SOAP extends HTTP and instead replace the SOAP functionality with GWT-RPC specifics: /org/apache/jmeter/protocol/http/control/gui/SoapSamplerGui.java /org/apache/jmeter/protocol/http/sample/SoapSampler.java Are there any others I should look at, or would this be considered a poor approach to extending Jmeter to handle GWT-RPC? *Previous work on another project required the use of HttpServletRequestWrapper to get the payload level of the GWT-RPC specifcs (example of common pipe-delimited format: dataitem1|dataitem2|dataitem3|dataitem4|dataitem5|dataitem6|dataitem7). I suspect that there will be a need for something similar in Jmeter and if there is recommendations to make this as efficient as possible that would be appreciated. I'm not promising anything at the moment, just want to evaluate the scope :-) Thanks! -D --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
