...
Tapestry's live class reloading is not perfect
![]() Wiki Markup |
{footnote:1}The perfect is the enemy of the good.{footnote}
|
. It tends to use a lot of Java ClassLoaders on top of the normal ClassLoaders used by the Java Virtual Machine and the servlet container. When you change non-component classes and interfaces that are referenced by components and pages, such as to add or change a method, only the component classes are reloaded. The non-component classes are frozen as they were when they were first loaded.
Unfortunately, this is one of the areas where you must restart your application entirely in order to force the new versions of the non-component classes to be loaded into memory.
![]() Wiki Markup |
{display-footnotes}
|
![]() Wiki Markup |
{scrollbar}
|
Specific Errors FAQ 