[
https://issues.apache.org/jira/browse/CXF-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-6094.
------------------------------
Resolution: Not a Problem
Assignee: Daniel Kulp
This is working correctly. If you don't configure the keystores that are
needed for the HTTPS connection, and the HTTPS connection isn't using a
certificate that is signed by one of the certificates that are built into the
JDK, it looks in the ~/.keystore file. If that file isn't there, then that
warning is displayed. The error is then that it cannot connect to that
service since it lacks a trusted certificate.
You can pass the various system properties described:
http://stackoverflow.com/questions/5871279/java-ssl-and-cert-keystore
to the command line tools to configure the keystore locations. For runtime,
the same system properties should work, but configuring the HTTPConduits is
generally the preferred approach. See:
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport(includingSSLsupport)-ConfiguringSSLSupport
> wsdl2java - Default key managers cannot be initialized
> ------------------------------------------------------
>
> Key: CXF-6094
> URL: https://issues.apache.org/jira/browse/CXF-6094
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.2
> Environment: java 1.7
> Reporter: member sound
> Assignee: Daniel Kulp
> Priority: Blocker
>
> C:\Users\Administrator\workspace\apache-cxf-3.0.2\bin> wsdl2java
> https://example.com/V1/HelpService?wsdl
> *Nov 03, 2014 1:11:20 PM org.apache.cxf.configuration.jsse.SSLUtils
> getDefaultKeyStoreManagers WARNING: Default key managers cannot be
> initialized: C:\Users\Administrator.keystore (The system cannot find the file
> specified)
> I'm getting the same error about 100 times if I start a soap webservice
> client that was autogenerated with cxf 3.0.1 but uses the new version 3.0.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
