DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10246>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10246 dynamic classdynamic class/jar loading mechanism [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|dynamic class |dynamic classdynamic |dynamic class/jar loading |class/jar loading mechanism |mechanism | ------- Additional Comments From [EMAIL PROTECTED] 2002-06-26 14:00 ------- Note that class unloading has some gotcha's. You can't reliably reload a class into the same classloader. If you use multiple classloaders which are siblings of each other in the classloader hierarchy, then the classes loaded in each classloader can't use the classes loaded in the other classloaders. Effectively, this means that you have to reload a whole classloader worth of classes to pick up a change to a single class. Also, if you're not careful, you might find it hard to get the previous classloader garbage collected as there will probably be many references to it from active objects. This could consume excessive memory. More background at: http://java.sun.com/docs/books/jls/unloading-rationale.html. Note also that class unloading is apparently still rather implementation dependent.
