Hi!
Rickard �berg skrev:
> The problem with this is that it is hard to change things. For example,
> the only classes in this system that are *really* static are the system
> classes (i.e. rt.jar and /jre/lib/ext classes). EVERYTHING else is
> potentially dynamic. The server code can be replaced at runtime, and the
> EJB classes can be (and typically are because of Hot Deployment)
> replaced. So, putting them all into one hashtable is not a good idea :-(
Unless you can figure out some way to have the classloader to remove their class
entrys from the hashtable when they are dying and then refill their class entrys when
going live again... But I understand that it is a whole lot a easier to let the
classloader handle their own hashtable and just drop them and then recreate it.
/Lennart
--
Lennart Petersson
mailto:[EMAIL PROTECTED]
http://www.benefit.se
Or try Yahoo! Messenger, my nickname is: en_grillad_special
