This is true for the most part. Once you manage to figure out how it works,
it really isn't that difficult to manage. The difficulty becomes when you
use common classes that span multiple ear files that are deployed to the
same instance. If you are actively developing and need to redeploy the common
classes, then you have to rebuild each ear that is deployed - the loaders
aren't isolated to the extent that each can have a different version of the
same class. It (JBoss) craps-out with a meaningless error message when this
Lyytinen Joonas wrote:
As far as I know, the classloader architecture is pretty much madated by
the J2EE spec, and there is not much that can be done with it.
From: Bavo De Ridder [mailto:firstname.lastname@example.org]
This currently gives me serious headaches with JBoss. Oh yes,
please make a
better classloading architecture compared to JBoss!