is this a bug in Axis2? I followed the instructions at:
http://wso2.org/library/1646:
"You can provide a virtual protocol name to be used with your new
socket factory as well. In order to do this, you just have to
register your new protocol with HTTPClient. Nothing else is required
to be passed in to Axis engine"
I did that but nothing works. I always get the error:
"Transport out has not been set"
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 1 Nov 2007, at 11:50, Alistair Young wrote:
typo, it should be:
Protocol authhttps = new Protocol("https", new
FedoraProtocolSocketFactory(keystoreLocation, keystorePassword,
truststoreLocation, truststorePassword, 443);
Protocol.registerProtocol("secure", authhttps);
Axis2 uses HttpClient but doesn't seem to understand "secure"
instead of "https". Registering "secure" as a protocol is enough
for HttpClient but not Axis2. Is there another step I need to do to
get Axis2 to work with "secure" protocol designator?
thanks,
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
On 1 Nov 2007, at 11:29, Alistair Young wrote:
I'd like to remap https to another "name", e.g. "secure" as I want
to use custom ssl handling with it. I've done this:
Protocol authhttps = new Protocol("secure", new
FedoraProtocolSocketFactory(keystoreLocation, keystorePassword,
truststoreLocation, truststorePassword, 443);
Protocol.registerProtocol("secure", authhttps);
it works fine using "https" but when I change it to "secure" I get
the error:
"Transport out has not been set"
when connecting to secure://service.url
is there a way to tell Axis2 how to handle "secure" - it's really
https in disguise
thanks,
Alistair
--------------
mov eax,1
mov ebx,0
int 80h
