Ulrich Meis wrote:
> I propose a different solution. [...]
This seems like a subset of the other solutions suggested. If you can
configure the SSLSocketFactory used, you can use a class just like the
one you provided without requiring that everyone uses it.
I'd rather see a flexible solution that can be customized to the needs
of a particular application. For example, the code that you provided
assumes that there is one global truststore and that it is a Java-format
keystore that is accessible locally. Neither of those are necessarily true.
-O
