HTTPS: custom keystore: regression in 2.2 from 2.1.3

[Vassilis Virvilis]

Hi everybody,

I have the following regression in https usage. My previous setup in 2.1.3 was 
working correctly with a custom keystore in resources. My cxf.xml was like this

<beans xmlns="http://www.springframework.org/schema/beans";
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xmlns:sec="http://cxf.apache.org/configuration/security";
        xmlns:http="http://cxf.apache.org/transports/http/configuration";
        xsi:schemaLocation="http://cxf.apache.org/configuration/security
                http://cxf.apache.org/schemas/configuration/security.xsd
                http://cxf.apache.org/transports/http/configuration
                http://cxf.apache.org/schemas/configuration/http-conf.xsd
                http://www.springframework.org/schema/beans
                http://www.springframework.org/schema/beans/spring-beans.xsd";>

  <http:conduit 
name="{http://lib.biovista.com/}UserSessionManagerPort.http-conduit";>
    <http:tlsClientParameters secureSocketProtocol="SSL">
      <sec:trustManagers>
        <sec:keyStore resource="resources/keystore.jks" />
      </sec:trustManagers>
      <sec:cipherSuitesFilter>
        <sec:include>.*</sec:include>
        <sec:exclude>.*_DH_anon_.*</sec:exclude>
      </sec:cipherSuitesFilter>
    </http:tlsClientParameters>
    <http:client Connection="Keep-Alive"/>
  </http:conduit>

</beans>

With 2.2 cxf doesn't pickup the correct keystore. It uses JRE's original 
keystore. Has something changed? Can I work around the problem?

If you think this is a good idea I will make a JIRA out of this post.

Regards

     .bill