What we've got right now is Axis 1.0 with a custom patch to use a single session cookie on multiple endpoints. Our client is a .NET 1.0 thick app, which may or may not migrate to .NET 1.1 real soon now.
I'm looking into upgrading our Axis to 1.1, but this may not happen for a while (till 1.2). I'm trying to use JMeter to imitate the .NET client. Without supporting the JSESSION cookie, I can't successfully maintain a session after I login. The headers are to handle the "Expect: 100-continue" and User Agent headers. User Agent probably isn't that important right now, but will be in the future. We are looking at ditching the cookie session solution soon and moving to SOAP headers. This is needed cause our SOAP needs to be transport neutral and handle thin clients that don't support cookies. As far as the overall improvements that I personally think would make doing WebService tests easier: 1. HTTP Proxy Server that has a TCPMON like listener, our .NET client doesn't handle proxies (we didn't write it so we can't add it). 2. Ability to suck data into User Parameter Preprocessor from a .csv file or to point it at a .csv file. That would work as one line == one set params so if you have 50 threads, thread 1 would get line 1 and line 51 from the .csv file as params. 3. Components of the same "type", ie WebServices Sampler, seems to "share" data on fields between instances in the GUI. I can give them unique values by hand editing the test plan xml. 4. On the WebServices Sampler, it doesn't seem to like our WSDL when trying to extract methods, not a big deal and we're using an old version of Axis. 5. Need to be able to use the HTTP Request Defaults with the WebServices Sampler. 6. We may only need the Session Cookie support you mentioned in your previous email, but I'm wondering if the Axis client uses that for multiple endpoints, which would follow HTTP rules, but we had to patch 1.0 to provide a single Session Cookie across endpoints. Would setMaintainSession(true) share this cookie to subsequent WebServices Samplers in a controller? I've done quite a bit of testing using JMeter and the HTTP Samplers previously, that worked superbly, other than some GUI and data import issues. If the WebServices stuff can match the quality of the HTTP testing I've done, I think that would be great. BTW, the Regex Extractor is awesome. I'm using it to pull session id stuff out of the SOAP message and pass it into the subsequent requests. If you want, I'll give the setMaintainSession fix a shot and let you know how well that works, but I'm sure myself or someone else will need the extra functionality we've talked about. Thanks a lot for your great work, JMeter works where a lot of other tools fail. Curt Johnson - [EMAIL PROTECTED] The Technical Resource Connection, Inc. http://www.trcinc.com -----Original Message----- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 10:42 PM To: JMeter Users List Subject: RE: HTTP Headers and Cookies in SOAP Requests replying to my own post again. I just took a look at the latest Axis and it looks like 1.2 is in alpha right now. Once it stabilizes, I plan to upgrade the webservice sampler to it and use wsdl4J also. my plan right now is to do after Jmeter 2.0 is released. peter lin __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
