[TAP5-2377] ComponentClassResolver should ensure that page names, component types, mixin names uniquely identify a single class

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 27/Aug/14 00:06
• Updated: 27/Aug/14 01:46
• Resolved: 27/Aug/14 00:31

Description

With all the special rules in play, package name stripping, etc., it can get a bit too confusing; extra validation is desired that identifies any situation where one logical name can map to more than one class.