Initially I just ran the test and it didn't work. I was assuming you would be picking the proxy parameters up off the command line. I was half way through an email to you about it still not working when I found the proxy entry fields (they were blank). Originally it was scrolled off the bottom of the window.
On reflection perhaps you are picking up the command line and just not showing it initially. After I entered the values they were always there on other tests I loaded (this is good). It is useful to have the check box to enable/disable proxy. However the values should come off the command line if they are there. The UI needs to maximise the space for the Soap Request message, width and depth. These could get rather large. The system lets me check use proxy and not put in an entry. There is no error generated for this. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] org]On Behalf Of peter lin Sent: Monday, 12 January 2004 09:48 To: JMeter Users List Subject: RE: Web Services Question Hi peter, I'm glad that worked for you. I will clean it up a bit. A couple quick questions regarding the UI. did it make sense to you that you have to check "use proxy" to enable it? Or would it make more sense to have it enabled always? any other thoughts you have about the UI is greatly appreciated. peter --- Peter Reid <[EMAIL PROTECTED]> wrote: > > I have downloaded 20040111 and it works - Yahoo!! > > Thank you for your help. > > I am happy to test any other changes you may want to > make in the future. > > > > > -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > org]On Behalf Of peter lin > Sent: Friday, 9 January 2004 17:02 > To: JMeter Users List > Subject: RE: Web Services Question > > > > I've checked in the changes to the sampler for proxy > support. I didn't fix the width issue yet. > unfortunately, I don't know the textfield well > enough > to set the width correctly. I gave it a quick try, > but > wasn't able to. > > I'll fix that later, once I find out from one of the > other developers. please get the latest nightly and > give it a try. > > peter lin > > --- Peter Reid <[EMAIL PROTECTED]> wrote: > > Perhaps you could make the WSDL URL, Web Methods > > drop down, URL, SOAPAction and "Soap/XML-RPC Data" > > dialog box full screen width for improved > > readability. > > > > I am happy to test all changes. > > > > I anticipate many hours for this projected. Jmeter > > will be the load and regression testing tool. > > > > > > -----Original Message----- > > From: > > > [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > org]On Behalf Of peter lin > > Sent: Friday, 9 January 2004 09:16 > > To: JMeter Users List > > Subject: RE: Web Services Question > > > > > > > > eeek, that sounds aweful. I'm sorry you have no > > choice. I'll make the change tomorrow and check it > > in over the weekend. when I'm ready, I'll send you > > an email. I don't use proxy's, so I will need > your > > help to test it out. > > > > how does that sound? > > > > > > peter lin > > > > > > Peter Reid <[EMAIL PROTECTED]> wrote: > > > > The issue is not that the Web Service uses the > > proxy, the company I am working in mandates a > proxy > > for all external traffic with Novel Border > > protection etc etc. This will often be the case. > > > > We have yet to establish an internal Web Service. > As > > such, in this environment, I cannot avoid the > proxy > > for external Web Services, and so cannot prove it > is > > the proxy causing the problem. However it looks > 99% > > certain to be that. > > > > Could you please implement the change, including > the > > command line proxy parameters, thus making it > > optional. > > > > I appreciate your help with this. > > > > -----Original Message----- > > From: > > > [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > org]On Behalf Of peter lin > > Sent: Friday, 9 January 2004 02:48 > > To: JMeter Users List > > Subject: RE: Web Services Question > > > > > > > > The current implementation is pretty simple. For > the > > wsdl url, I use the standard JMeter connection > > classes, so proxies do not affect it. The actual > > call using apache soap currently doesn't account > for > > proxy. My reasoning (probably flawed) is a > > webservice shouldn't be using a proxy, since it > > would pose a security risk. I may be a bit > paranoid > > here, but the webservices I've worked on need to > be > > secure. My personal bias is proxy servers can log > > traffic and I don't trust them. Of course, if you > > use SSL then it's secure, but the added cost of > SSL > > and XML would make the application slower than a > > snail. > > > > the code excerpt I included in the previous email > > shows exactly how to use apache soap in the case > of > > proxies. The current implementation in the sampler > > does this. > > > > > > Message msg = new Message(); > > > > RESULT.sampleStart(); > > > > msg.send(this.getUrl(), this.getSoapAction(), > > msgEnv); > > > > SOAPTransport st = msg.getSOAPTransport(); > > > > For Jmeter, I think it should support proxy. If > you > > can do me favor and try it from a connection that > > doesn't use http proxy to see if it works for you. > > If it works without proxy, I can safely assume the > > proxy is the cause. > > > > peter lin > > > > > > Peter Reid > > wrote: > > On my site the WSDL query that populates the > > services drop down works. > > I assume this is not a soap call and will be using > > the proxy (as specified on command line) > > > > It is the Soap requests that do not work and do > not > > show any activity on a "proxy http inspector" tool > I > > have been using to look at request/responses from > > Jmeter. > > > > How does the Soap Sampler do it? > > > > I think we just need the Soap to proxy calls > > implemented for the Web Services Sampler > > > > -----Original Message----- > > From: > > > [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > org]On Behalf Of peter lin > > Sent: Thursday, 8 January 2004 16:07 > > To: [EMAIL PROTECTED] > > Subject: RE: Web Services Question > > > > > > > > I did a search on apache soap site and it appears > > proxy's have to be handled differently. > > > > my currently implementation assumes a direct > > connection. In order to use proxy, I may have to > > change the way I use apache soap. from the soap > faq. > > > > 2.28 How do I tell my Apache SOAP client to use a > > proxy server? > > Here is some sample code to do this: > > SOAPHTTPConnection connection = new > === message truncated === __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
