Hi!
Lennart Petersson wrote:
> Probably have you already thought of this but...
>
> Would it be possible to only have one hashtable with all classes in an ordered
> sequence with classes from beanloader first and then classes from apploader and
> serverloader. (I guess systemloader is handled in a more standard way if no hit
> from other loaders?). In this way you would only have one hashtable to search.
>
> Problem is where to have this hashtable and how to make the different loaders to
> fill it up, or?
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 :-(
Fortunately the current hashtable implementation *is* fail-fast, but
it's still a step that will consistently fail during serialization. Or
so I would guess. I might be completely wrong here.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
