I still have this gut feeling that we need to rethink how
MarshalledObject is used and how we might make the whole mechanism
managed more as a Thread or ThreadPool based mechanism instead of a
whole JVM mechanism. It is true that context class loader mechanisms
help contain the view of foreign classes. But we need the ability to
"allow injection" of unmarshalling support classes so that a service
can be more independent of the clients environment. I don't have a
clear view of what yet, I'm just mulling around about this.
Gregg Wonderly
There are multi-threading issues with ClassLoaders, JVM 7 addresses
these issues. Separation of Classloading into one thread perhaps? Like
Swing? Don't know myself either, just some thoughts.
Cheers,
Peter.
