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 > SOAPHTTPConnection(); > connection.setProxyHost("proxy"); > connection.setProxyPort(8080); > Call call = new Call(); // prepare the service > invocation > call.setSOAPTransport(conn); // use the proxy > > > can you verify it is caused by proxy? once you do, I > can make the change and add the option to the > sampler. > > thanks. > > > peter lin > > --- Peter Reid > wrote: > > Hi, > > > > I just tried the latest nightly 20040106 and got > the > > same problem. > > > > Could it be some thing to do with using a proxy? > > > > > > > > > > > > -----Original Message----- > > From: peter lin [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 8 January 2004 09:24 > > To: Peter Reid > > Subject: RE: Web Services Question > > > > > > did the sample test plans I sent you help? if not, > > please let me know. > > > > peter lin > > > > > > > > > > > > _____ > > > > Do you Yahoo!? > > Yahoo! Hotjobs: Enter > > > > > the "Signing Bonus" Sweepstakes > > > > > > > ------------------------------------------------------------------------------ > > "This communication, including any attachments, is > > confidential. > === 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]
