Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 7502 invoked from network); 29 Oct 2008 04:07:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Oct 2008 04:07:09 -0000 Received: (qmail 71685 invoked by uid 500); 29 Oct 2008 04:07:11 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 71671 invoked by uid 500); 29 Oct 2008 04:07:11 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 71649 invoked by uid 99); 29 Oct 2008 04:07:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Oct 2008 21:07:11 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.252.110.199] (HELO web56105.mail.re3.yahoo.com) (216.252.110.199) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 29 Oct 2008 04:05:54 +0000 Received: (qmail 30553 invoked by uid 60001); 29 Oct 2008 04:05:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=nmw8l4SIv/h2rRxgg2BVTrRfk6nB4IUP5DT7DD2FJOCrZ3fr/7erRKUkhomZuPjmrNT7GdNV7/KNJSf2QmVL9CJU7w2eMmjt6Byio0Y82k0s1gG/eBtmr8J45afzKDcYqcd8ISgti5onTJtcJAUvWTX1ruJ1blBs54vPcGwYUqQ=; X-YMail-OSG: cTtAfZUVM1lbkjLteeKS8SMKaIzi6bTPC9UOhwUtOdppZXkA1BOqGTqkSzg6vVUFJGBoHLm_6JZhrJRLwp9IL3aM2QA.2USZIz0C_Wz6qF0.WMoRoDczo5i_zKJAZJxEEtwrPKQMIJnbtWsBornDSYqF80n5mCN73cxFjYjy7BNur4PGdITxPxbVL00- Received: from [75.7.8.125] by web56105.mail.re3.yahoo.com via HTTP; Tue, 28 Oct 2008 21:05:30 PDT X-Mailer: YahooMailWebService/0.7.247.3 Date: Tue, 28 Oct 2008 21:05:30 -0700 (PDT) From: Vivian Wang Reply-To: vivianwangym@yahoo.com Subject: a HTTPS/SSL question To: axis-c-dev@ws.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <512547.30446.qm@web56105.mail.re3.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, there, I have a web service client using axis2/c to access a Salesforce.com web site that is protected with SSL (the url starts with https://). I didn't give a certificate chain file path in the configuration file axis2.xml, so the web service client failed. However, if I use soapUI (a free downloaded web service testing tool) to access the same serivce without giving any SSL related setting (just like accessing a service starting with http://), it all goes fine. What is the difference here? Is there any setting I can do in axis2/c to make it work as soapUI? I noticed another similar thing. When a wsdl parser (from axis-j 1.4) tring to retrieve a SSL-protected wsdl (I set it up in TOMCAT) using a URL that starts with https:, I have a provide a client keystore (using jsse system.setProperty(....)) otherwise I will get an error saying something like trustedstore not found, but soapUI was just fine loading the same wsdl. What's really going on? Any help is much appreciated! Vivian --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org