Jeremias Maerki wrote: > As far as I know, you can't assume that, because the statics > are global within the context of a ClassLoader and not the JVM. > Normally though, you have only a simple ClassLoader hierarchy. > In that case your assumption is right. But it isn't as soon as > some complex classloading is done (as in EJB servers, > web containers, Avalon Phoenix etc). In that regard, Arnd could > (probably!) have run two differently configured FOPs in one VM, > but not without major headaches, I think. That's why I personally > would like to get rid of all unneccessary statics that could > be in the way of using FOP in a multithreaded and multi-configuration > environment.
If I remember correctly from the Java 2 VM specification, a class specification is actually a combination of the full package name and - the "defining" class loader. If a class of the same package name is loaded (ok, "defined", to be precise) by two different class loaders, then these two classes ARE really considered different. This is roughly similar to the problem with class and package names: java.sql.Date and java.util.Date ARE different classes. So, technically, globals ARE unique within a VM. This may sound like nit-picking, but then perhaps it's not. Not that I would advocate using statics based on this.. 8-) If you think I'm wrong in this, please tell me. I think I know a few places where I rely on this (hopefully correct) knowledge. Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
