axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dumindu Pallewela" <>
Subject Re: HTTPS support -- different implementation from AXIS-J
Date Wed, 13 Feb 2008 06:05:07 GMT
Hi Vivian,

> Hi All,
> I was looking at AXIS2/c manuals and reading through the mailing list
> regarding HTTPS support, I noticed that the HTTPS support in AXIS2/c  is
> different from AXIS-J. I was using AXIS-J for a while in the past,  and I
> remember that in order to support HTTPS in the Client side, I will need a
> keystore file, and all I need to do is to set a System property like this
> following
> in the java clinet before making the web service call:
>         System.setProperty("", keystorePath);
> Here in AXIS2/c, it seems require a key chain file, is this key chain file
> the same thing as that keystore file? I notice that the way to create these

No they are not.

> two files are somewhat different. Also in AXIS2/c, there is a extra
> passphrase, which does not seem to be in the AXIS-J. Is this passPhrase a
> must have in order to support HTTPS?

I'm not sure why a passphrase is not used in AXIS-J, but here it is
used in order to protect the private key. You can choose to encrypt
your private key when you create one. Thus, if your private key is not
encrypted with a passphrase you do not have to provide this.

> I am also wondering if there is a service APIs to set the keyChain file (or
> file path) in the call object, or something like the above example in java
> (set System property)?

I'm afraid it is not as simple in AXIS2/C though it is not too
complicated either :). Please refer to AXIS2/C manual [1].



Dumindu Pallewela
GPG ID: 0x9E131672

WSO2 | "Oxygenating the Web Service Platform" |

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message