Hi
On 15/09/15 18:09, Messner, Friedrich (Allianz Deutschland, externer
Mitarbeiter) wrote:
Hi,
I've developed a Spring application which runs on a Websphere with configured
SSL keystore. I tried to find out how to configure a CXF client to use the
Websphere-provided SSLSocketFactory (obtained with
com.ibm.websphere.ssl.JSSEHelper). There seems to be a property for exactly
that in org.apache.cxf.configuration.jsse.TLSClientParameters but it is not
exposed via Spring-DSL. So I ended up with an interceptor in phase SETUP which
sets the programmatically created TLSClientParameters to the message's
HTTPConduit. This is obviously not the most efficient solution since it has to
be done for each call instead of doing it once on application start.
Do you mean you have to create a new instance of TLSClientParameters on
every request ? Perhaps you can have a single shared instance used
between the requests...
I know that there is another option to configure the client programmatically
but this is ugly as well since then a user gets a half wired client and has to
do additional setup before using it. So I'm searching for a solution to
configure the client completely within Spring. I thought of writing my own
Spring FactoryBean to setup the HTTPConduit but it is quite hard to find a good
starting point for doing so.
Is there any clean Spring approach or at least a better solution than an
interceptor?
Sorry, have no idea myself but may be someone else can help...
Sergey
Thanks & regards
Friedrich
