I have a question. Consider scenario:
JRE has java.security configuration file that includes list of providers. At some (usually start-up) time this file is being loaded and parsed. Then providers are loaded too and list of available algorithms is created. Some algorithms or even whole providers might require native libraries, those libraries could be unavailable at the moment of load attempt. If the libraries are unavailable we have the following options: 1. Do not include algorithm that requires unavailable libraries into the list of available algorithms. 2. Do not include whole provider 3. Terminate VM It is reasonabe that 1&2 are supplemented with some logging. RI seems to do #2 plus logging. What should we do if logging is prohibited? Thanks, Mikhail 2006/5/31, Geir Magnusson Jr <[EMAIL PROTECTED]>:
Tim Ellison wrote: > Geir Magnusson Jr wrote: >>> The logging info being proposed is developer-oriented. I hope that >>> people are not expecting our users to understand our developer trace >>> info -- we, as developers, have better tools than printf to figure out >>> what is happening. >> I have to admit that I don't agree w/ "better" as a universally general >> statement, > > Well I guess it is a POV, but give me a java-aware debugger and trace > tools over printf any day. To be clear [again], don't get caught on "printf", because no one is advocating that, I believe. geir --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
