The consequence of what Simon says is that you have to be prepared to have a separate init for each jvm and this can cause issue if your application relies on the semantics of a single init (singleton, etc..)
regards didier On Mar 31, 1:55 pm, Simon Knott <knott.si...@gmail.com> wrote: > Static initializers will be thread-safe, but you've got to remember that > that class may be loaded in multiple JVMs, depending on how many instances > get spun up for your application. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
