[
https://issues.apache.org/activemq/browse/SM-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39932
]
Guillaume Nodet commented on SM-1029:
-------------------------------------
This is good news ? We really need more people involved in ServiceMix
development.
You will find information on creating patches at
http://incubator.apache.org/servicemix/contributing.html
Just attach your patch to a JIRA issue ...
See also
http://incubator.apache.org/servicemix/becoming-a-committer.html
> Bug in HTTP BC when configuring managed keystore for SSL
> ----------------------------------------------------------
>
> Key: SM-1029
> URL: https://issues.apache.org/activemq/browse/SM-1029
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: 3.1.1
> Environment: ServiceMix deployed on Windows XP
> Reporter: Will Franco
> Priority: Minor
>
> The problem is that ServiceMixSslSocketConnector extends SslSocketConnector,
> and it is providing its own data member and getter/setter for the trust
> store, named "trustStore". However, SslSocketConnector already declares a
> data member and getter/setter for the trust store, named "_truststore".
> The bug is manifested in JettyContextManager.createServer(URL url,
> SslParameters ssl) method, when the "managed=true" is included in your
> SslParameters. The initialization of the ServiceMixSslSocketConnector calls
> "setTruststore" method which sets the "_truststore", eventually, there is a
> call to ServiceMixSslSocketConnector.createFactory() method, and in its
> implementation, it passes in the value of the "trustStore" that has never
> been set, instead of the value of "_truststore".
> This bug is affecting the option of having a managed trust store for SSL.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
