Voting at DZone is super easy, but you aren't logged in. Login and vote now.
By ekabanov
via zeroturnaround.com
Published: Mar 10 2010 / 07:39
Over the Reloading Java Classes (RJC) article series, we’ve examined how class reloading happens, from objects and classloaders to application servers and solutions that reduce Turnaround. It’s been pretty in-depth, so we’d like to take a step back, move to more shallow ground, and take a look at why we would want class reloading to work in the first place. What are the real costs of missing class reloading on Java teams?
Add your comment
