Although it's up to staff to judge - don't skip around between several accounts and topics while you try to ask for a solution to an issue - stick to the account and topic originally used to ask the initial question. Also, if you do crossposting on several sides - please, be so fair to at least include a note to each others site/thread for link up to enable others to easy check if the question has already been answered.
Anyway - as someone quite into all that crypto stuff: from as far as I understand the posted code and the question: There's no difference other than the former has a global impact to all getDefault() calls within the whole VM while the second one only cares about instances directly derived from the sslContext you set up.
Or, in other words: calling a setDefault() in the latter example would end up in the same result.
From wherever you got that from: It's mostly pointless as for a client you usually don't override any of the crypto stuff - and for a server you most often end up with your own SSLContext instance anyway.
The harder you work, the luckier you get. This tiny ad brings luck - just not good luck or bad luck.
SKIP - a book about connecting industrious people with elderly land owners