Stephen McConnell wrote:
Your creating different instances of the same class in different classloaders. Bottom line is that the class must be *shared* which means that the APIs must exist in a classloader that is common to both the consumer and the supplier - i.e. a common parent as you discovered.
So... my clever attempt to prevent having to load a gaggle of jars in the common parent backfired when I thought my interface methods could return byte[] instead of an instance of MyLegacyObjectThatRequiresFifteenFreakingJarsInTheClassLoader?
Passing a byte[] isn't going to cause a problem. If fact it would not even matter of te implementation classes were different between your two containers (because they would not be exposed to each other). I figure you should be looking for something else your exposing on the API that is causing the problem.
Stephen.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
