on 3/13/02 1:50 PM, "James Taylor" <[EMAIL PROTECTED]> wrote:
> Unfortunately JCS requires predictable initialization orders in a lot of
> these cases (things must be configured before getCacheManager is called
> for example). I don't know how safe it is to rely on the classloader for
> this case. It seems like we have to incur the cost of synchronizing the
> 'ensureCacheManager' method if we want to be truly safe.
>
> Thanks,
> James
The initialization of the static{} is predictable. In fact, it is documented
that it happens before the constructor is called. Read the Java language
spec.
-jon
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
