Jamie Nicolson wrote:
> Steven T. Hatton wrote: > >> I may be overly pedantic in my coding style, but I try to catch each >> exception explicitly using a separate catch block for each Exception >> class. In attempting to do this with >> org.mozilla.jss.CryptoManager.NotInitializedException I discovered it >> is package scoped. Is there a reason for this? It seems to be >> stylistically incorrect. > > > Not sure what you mean by "package scoped". It is a nested class, but it > is public. Do you mean that you have to refer to it as > "CryptoManager.NotInitializedException" instead of just > "NotIntitializedException"? I don't feel very strongly about it either > way, so I'd just as soon leave it the way it is. > Yes indeed, I stated that incorrectly, and now realize that I can access it. I agree that it is not a major issue. My own personal experience makes me believe not nesting it would be better, in so much as it conforms to what I typically expect from other Java SDKs. I may not be the ideal test case, but I believe the fact that I asked about it shows it to be a potential problem. But as you say, it ain't no big thing.
