Although I am strictly a Java guy (no ms :) ) I can understand your position.
Those properties you use for hostname & port for the proxy are used when you run
your WSDL2Java. You include those properties in the whole line so you will run the following:
java -Dhttp.proxyHost=my.proxy.host -Dhttp.proxyPort=my.proxy.port org.apache.axis.wsdl.WSDL2Java service.wsdl
This is how you define(D) variables before executing your code (in this case WSDL2Java). Make
sure you replace my.proxy.host with the proxy hostname, and my.proxy.port with the proxy port.
Although I do not have any experience using a proxy for this I think this should work. If not hopefully
somebody with more information will chime in.
Anthony
On 1/23/06, Girish_Kumar <[EMAIL PROTECTED]> wrote:
Dear Anthony,
First let me thank you for this quick response. I have been waiting for a long time for someone to respond on my problem.
My web service is actually a microsoft WCF(Indigo) implementaion and I am trying to generate proxies using Axis/Java. Here I am facing the unknownhost exception. I tried setting proxy login credentials thru Java plug-in component in control panel. I am simply using the following command to generate the proxies:
java org.apache.axis.wsdl.WSDL2Java service.wsdl
This works fine in my personal laptop where I do not have any proxy setup.
Based on some info found in some web site I created some system variables similar to that you explained in this reply:
-Dhttp.proxyHost=hostname
-Dhttp.proxyPort=80
Now I feel what I did was wrong. Can you please specify how and where to set these properties?
To be frank I am not a Java programmer, but a technology curious guy. My current task is to check inter-operability between Java and MS Web services(Java/AXIS and MS WCF). After this I want to see consuming a Java/AXIS webservice by MS ASP.NET client.
Though I am not a Java programmer, I can develop java applications of any nature with confident.
Regards,
Girish Kumar
________________________________
From: Anthony Bargnesi [mailto:[EMAIL PROTECTED]]
Sent: Mon 1/23/2006 10:43 PM
To: axis-user@ws.apache.org
Subject: Re: Reasons why Webservice is inaccessible from WAN?
Girish,
The documentation for ant wsdltojava says:
Create Java classes from local or remote WSDL. Mappings from namespaces to packages can be provided as nested <mapping> elements.
Proxy settings are taken from the java runtime settings of http.ProxyHost, http.ProxyPort, etc. The Ant task <setProxy> can set these. As well as the nested mapping elements, this task uses the file NStoPkg.properties in the project base directory for namespace mapping
So either use setproxy <http://ant.apache.org/manual/OptionalTasks/setproxy.html > (ant) or use
-Dhttp.proxyHost=hostname
-Dhttp.proxyPort=80
Full properties for JDK 1.4.2 can be found here < http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html> .
HTH,
Anthony Bargnesi
On 1/23/06, Girish_Kumar <[EMAIL PROTECTED]> wrote:
Hi,
How do we bye pass or authenticate a proxy while using wsdltojava?
Girish
________________________________
From: Anthony Bargnesi [mailto: [EMAIL PROTECTED]]
Sent: Friday, January 20, 2006 10:24 PM
To: axis-user@ws.apache.org
Subject: RE: Reasons why Webservice is inaccessible from WAN?
Do you have a proxy server?
You can test the service access with a browser.
tao
I am not running a proxy server on the client. The server I am not too sure
about. I know, though, that I can do a "wget" command from my linux box
and access the service. I have retrieved the "webservice exists here page"
as well as querying for the wsdl with ?wsdl. Those both work from my client
but when using the axis client api it hangs without making a soap request.
Anthony Bargnesi
DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated..
DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.
