Yes I agree. If JSS could return the SSL/NSS error codes when SSLSocket (I incorrectly referred to SSLServerSocket in original posting) gets an error on connection, that would be great (Class could be something like jss.ssl.SocketException which would subclass java.net.SocketException). As you said, I can then do a switch on the integer SSL return code to get the error description.
Naturally this new class could also be used in SSLServerSocket. Should I submit this request in bugzilla or did you do that? -- P "Jamie Nicolson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > > > Patrick wrote: > > >To follow up on recently submitted fixes to SSLServerSocket, SSLServerSocket > >should also throw a java.net.ConnectException when it gets a connection > >refused by peer error (SSL error -5981), instrewad of the generic > >java.net.SocketException... > > > >Actually, maybe JSS should have a subclass under java.net.SocketException > >for each SSL exception that can occur...That would make for a lot more > >user-friendly JSS error reporting :) > > > >What do you say? > > > A separate class for each error code seems excessive given that there > are over 100 of them. Maybe one or a few SSL exception classes which > contain a specific error code? It's probably more efficient anyway to > switch on an integer error code than to have a list of catch blocks, > each of which does a string comparison on class name. > >
