Rodrigo Kumpera wrote:
There is a long track of incompatibilities between JVMs and most of
then are subtle, poor specified behavior. A good example is
java.util.ConcurrentModificationException, this exception is thrown in
a best-effort way by the Collection classes. This means that JVMs will
Breaking out of lurk mode, I'll be at J1 as well, and would be interested in
any (non-prime-time) conversations that get set up -- at least as a fly on
the wall.
-jn-
--
my morning coffee
middle-aged american
tea ceremony
You could play class loader games, however those could be
circumvented by just another customized class loader.
Doug Lea discussed the general issue in a message to this mailing
list already. IMHO the problem is, that you can make a class only
public, package-private or visible for a single class
