ays that I can set the trust and key stores, basically
>>> the
>>> SSLContext. Currently what we are thinking is that we will be using the
>>> SSLContext.setCurrentSslContext(>> dump
>>> it here>).
>>>
>>> Is there any better approach.
e
>> pluggable, s.th that we can use across multiple JMS providers.
>>
>> Also why is the method setKeyAndTrustManagers marked as deprecated and
>> what
>> is the workaround for the same.
>> --
>> View this message in context:
>> http://www.nabble.com/Alte
s the method setKeyAndTrustManagers marked as deprecated and
> what
> is the workaround for the same.
> --
> View this message in context:
> http://www.nabble.com/Alternatives-for-deprecated-setKeyAndTrustManagers-in-ActiveMQSSLConnectionFactory-tp22724170p22724170
will be great if we can get anything
> more pluggable, s.th that we can use across multiple JMS providers.
>
> Also why is the method setKeyAndTrustManagers marked as deprecated and
> what is the workaround for the same.
>
--
View this message in context:
http://www.nabble
nd what
is the workaround for the same.
--
View this message in context:
http://www.nabble.com/Alternatives-for-deprecated-setKeyAndTrustManagers-in-ActiveMQSSLConnectionFactory-tp22724170p22724170.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
