[TAP5-1665] Tapestry could create non-singleton services more efficiently

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3, 5.2
• Fix Version/s: 5.3
• Component/s: tapestry-ioc
• Labels: performance
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 23/Sep/11 20:49
• Updated: 24/Sep/11 05:31
• Resolved: 24/Sep/11 04:54

Description

For services that may be created again on each request, Tapestry does a lot of extra work to analyze the class, constructor and fields. It should be able to roll up all this information into a repeatable "plan" that can simply be re-executed on each subsequent instance creation.