[TAP5-2742] Smarter page cache invalidation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 5.8.3
• Component/s: tapestry-core
• Assignee: Thiago Henrique De Paula Figueiredo
• Reporter: Thiago Henrique De Paula Figueiredo
• Created: 17/Nov/22 22:55
• Updated: 03/Aug/24 15:38
• Resolved: 17/Jun/23 22:11

Description

Since Tapestry 5's inception, it throws the whole set of assembled page instances when anything related is changed, be it the class itself, its template and maybe also associated messages and assets. In very large projects with large pages, this can reach a point it slows down the user (programmer) productivity, forced to wait for unchanged pages to be reassambled.

Tapestry should provide some way for users to segment page, component, mixin and base classes to separate regions, one for each classloader, to avoid clearing out cached page instances that don't have themselves or the classes they use changed.

Issue Links

• causes: TAP5-2770 With multiple classloader mode on, ClassCastException when component and superclass both have @Import
• causes: TAP5-2772 ClassCastException happening in some cases in production mode
• relates to: TAP5-2762 New symbol for defining the path to the component dependencies file
• mentioned in: Page Loading...