RE: [Axis 1.2] WSDL2Java for HTTPs url throws exception.

[subir.sasikumar]

OK I will try again a few other scenarios to see whether that is correct. Thanks for the reply.   Subir S Wipro Technologies, Survey No: 64, Madhapur, Hyderabad-500081, AP tel: 040-30795137     Want a signature like this?    From: Remy Bertrand [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:16 AM To: axis-user@ws.apache.org Subject: Re: [Axis 1.2] WSDL2Java for HTTPs url throws exception.   The problem is not that WSDL2Java cannot resolve IP address, it's that https protocol enforce that the name of the certificate must correspond to the server host.   If you generate the certificate with name topaz.subir.com, you have to give this name to WSDL2java, not the IP address.   If you were doing that in a browser, you would have an alert because the name in the certificate doesn't correspond to the hostname. In a Java program, this is an exception...   And lasts, your client probably uses the host name in his own code, thats why he can connect to the service.   Rémy ----- Original Message ----- From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Wednesday, June 14, 2006 11:50 AM Subject: [Axis 1.2] WSDL2Java for HTTPs url throws exception.   Hi,   I am getting a weird error when trying run WSDL2Java using https connection.   I have SSL enabled using mod-ssl in Apache server connected to tomcat server using JK2.   Jdk is 1.5.0_03, tomcat 5.0.9, apache 2.0.52   I use the following to generate the stubs   java -Djavax.net.ssl.trustStore=C:\TraceLogs\tempstore.jks –Djavax.net.ssl.trustStorePassword=subir123 org.apache.axis.wsdl.WSDL2Java https://192.168.134.145:443/prwp/services/UploadServices?wsdl -p prwp.soapclient -o .   I get the following exception.   java.io.IOException: HTTPS hostname wrong:  should be <192.168.134.145>         at sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.j ava:493)         at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java: 418)         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect (AbstractDelegateHttpsURLConnection.java:170)         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon nection.java:913)         at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Http sURLConnectionImpl.java:234)         at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrent Entity(XMLEntityManager.java:973)         at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineD ocVersion(XMLVersionDetector.java:184)         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:798)         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:764)         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser. java:148)         at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser. java:250)         at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Doc umentBuilderImpl.java:292)         at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:369)         at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:420)         at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:480)         at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)         at java.lang.Thread.run(Thread.java:595)   The host name corresponding to the IP address 192.168.134.145 is topaz.subir.com A dummy server certificate is generated by giving the common name (CN) as topaz.subir.com.   If I don’t try to generate the stubs using https but as http itself and manually change the http to https in the generated stubs, my client is able to access the services (even though I use IP address).   Any idea why WSDL2Java can not resolve the ip address but my client can do that.     Regards, Subir S Wipro Technologies, Survey No: 64, Madhapur, Hyderabad-500081, AP tel: 040-30795137     Want a signature like this?    The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com   The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com