[TAPESTRY-1975] Template parser is insufficiently picky about component ids

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.6
• Fix Version/s: 5.0.7
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 13/Dec/07 19:25
• Updated: 13/Dec/07 20:32
• Resolved: 13/Dec/07 20:32

Description

The template parser should complain if component ids are invalid ... they must be Java identifiers. People keep putting periods into the component id, ex:

<t:textfield t:id="user.firstname"/>

when they should:

<t:textfield value="user.firstname"/>

The fact that the parser allows the invalid component id, and then complains about it later and obscurely, is confusing.