On 09/09/2014 18:14, Naoto Sato wrote:
It's an inherent issue where some init code issues locale sensitive
services, such as in this case, *Formatter. So this could happen not
only in Security class, but could be anywhere. So I think we still
need the change proposed here in order for avoiding regressions. On
error cases, the diagnosability will be addressed with the issue with
8057075.
I think we should move this issue to security-libs and have this issue
addressed in the PolicyFile/PolicyParser code.
My concern with catching Throwable is that it's just going to make it
harder to diagnose tricky issues like this. I would be interested in
other possible cases where you think the ClassCircularityError might
happen. I'm just wondering if we need to approach this issue a bit
differently.
-Alan
