You need 2 different webapps
one which implements SunFakeTrustSocketFactory for implementing unsigned
server certs
..which would NEVER be used in Production Environment
this would allow someone's client to hack in with their own self-signed certs
one which implements
No. I have a web service client that uses axis1 to consume web services from
server A and server B. For server A I need to do authentication while for
server B there is no such need. So the problem is on my client side where I
need to configure axis to do authentication on some of the requests
I think that the socket factory is cached. Therefore changing the
properties after the first request will have no effect.
What I would do is to write my own socket factory that implements the
necessary logic to distinguish between the two cases.
Andreas
On Wed, Nov 14, 2012 at 9:42 PM, am am
So AxisProperties is global? From the docs it is unclear if they are bound to
threads or classloader
From: Andreas Veithen andreas.veit...@gmail.com
To: java-user java-user@axis.apache.org
Sent: Wednesday, November 14, 2012 10:51 PM
Subject: Re: Axis SSL
Sure properties are global, this kind of info is cached
Regards
Date: Wed, 14 Nov 2012 22:14:23 -0800
From: akme...@yahoo.com
Subject: Re: Axis SSL authentication help!
To: java-user@axis.apache.org
So AxisProperties is global? From the docs it is unclear if they are bound to
threads or
