Alexey Varlamov wrote: > Can't we use lazy initialization here? I had similar experience with > this class in the past, and think it should not be so fragile to > initialization sequence. And definitely it should not affect whole VM > run.
It's tricky to ensure the initialization sequence is solid when dragging in these types, but I agree with lazily initializing the resources in the Msg class; especially if it fixes this problem. Regards, Tim -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
