Oops, my mistake. I should have pasted this:
client.setProperty(CommonsHttpMessageSender.DISABLE_PROXY_UTILS,
"true");
client.setProperty(CommonsHttpMessageSender.HTTP_PROXY_HOST,
"intproxy.biperf.com");
client.setProperty(CommonsHttpMessageSender.HTTP_PROXY_PORT,
"8080");
As this is how I set the properties -- using the defined constants.
What you see below is just some playing around I was doing in
desperation. Unfortunately it still doesn't work.
-----Original Message-----
From: Tomek Sztelak [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 10:19 AM
To: [email protected]
Subject: Re: [xfire-user] Web Service Client that uses HTTP Proxy
No, no, no :)
The way you do it is ok and should work. Except that you are using
https.proxyPort :D try to use http.proxyPort an http.proxyHost (
without "s" in http )
On 3/16/07, Asleson, Ryan <[EMAIL PROTECTED]> wrote:
>
> I see. The only way to set HTTP proxyHost and proxyPort values is by
> using the dynamic client, right? I'm only using a Client because I
> thought that was the only way to specify the proxy host and port.
>
> Right now I create the client by using the Client.getInstance()
> method, passing to it an instance of my SOAP service:
>
> ReceiveClient service = new ReceiveClient();
> ReceiveSoap receiveClient = service.getReceiveSoap();
>
> //create a Client and set the properties for the proxy (proxy
> name and port)
> Client client = Client.getInstance(receiveClient);
>
> client.setProperty(CommonsHttpMessageSender.DISABLE_PROXY_UTILS,
> "true");
> client.setProperty("https.proxyHost", "proxy.biperf.com");
> client.setProperty("https.proxyPort", "8080");
>
>
> So how do I create the Client, specifying the URL, and also specifying
> the SOAP class? I see there's a constructor that takes a URL and a
> Class, but that doesn't seem right since I have an *instance* of the
> service (not a class), and the getInstance method takes an Object, not
> a Class. Do I just use the getInstance method to create a Client, and
> then use the setUrl() method?
>
> BTW, do you know offhand what the JIRA number for the issue is?
>
> Thank you!!
>
> -----Original Message-----
> From: Tomek Sztelak [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 16, 2007 10:00 AM
> To: [email protected]
> Subject: Re: [xfire-user] Web Service Client that uses HTTP Proxy
>
> WSDL is need if you are using dynamic client like Client client = new
> Client(WSDL_URL); If you are not using such, then wsdl isn't
downloaded.
>
> On 3/16/07, Asleson, Ryan <[EMAIL PROTECTED]> wrote:
> >
> > If I download the WSDL to my local drive, how do I tell Xfire to use
> > that WSDL instead? And I'm just curious -- why does Xfire need to
> > get
>
> > the WSDL?
> >
> > If I get a work around figured out I could try looking at building a
> > long-term patch.
> >
> >
> > -----Original Message-----
> > From: Tomek Sztelak [mailto:[EMAIL PROTECTED]
> > Sent: Friday, March 16, 2007 9:18 AM
> > To: [email protected]
> > Subject: Re: [xfire-user] Web Service Client that uses HTTP Proxy
> >
> > >Thanks for the info. Could you explain a little more on how to get
> > around this problem? I >thought XFire used Commons Http Client
> > under the covers anyways.
> >
> > HttpClient is used during method execution, not for WSDL retrieving,
> > what apparently should be changed.
> >
> > >XFire devs, can you comment on whether this is a known issue and
> > >any
> > endorsed work >arounds?
> >
> > sure: its known issue :) we even have jira issue about that. As a
> > workaround you can download wsdl to your local drive and use it from
> > there.
> >
> > I'll look at this just after i get my internet connection at home
> > back, what can take a while ( like few weeks, so BIG hello to my net
> > provider here ) . But if any of you want create patch with fix, it
> > would be great :D
> >
> > --------------------------------------------------------------------
> > - To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> > This e-mail message is being sent solely for use by the intended
> recipient(s) and may contain confidential information. Any
> unauthorized review, use, disclosure or distribution is prohibited.
> If you are not the intended recipient, please contact the sender by
> phone or reply by e-mail, delete the original message and destroy all
copies. Thank you.
> >
> > --------------------------------------------------------------------
> > - To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
>
>
> --
> -----
> When one of our products stops working, we'll blame another vendor
> within 24 hours.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
> This e-mail message is being sent solely for use by the intended
recipient(s) and may contain confidential information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not
the intended recipient, please contact the sender by phone or reply by
e-mail, delete the original message and destroy all copies. Thank you.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
This e-mail message is being sent solely for use by the intended recipient(s)
and may contain confidential information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by phone or reply by e-mail, delete the
original message and destroy all copies. Thank you.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
