Tapestry
  1. Tapestry
  2. TAPESTRY-1975

Template parser is insufficiently picky about component ids

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.6
    • Fix Version/s: 5.0.7
    • Component/s: tapestry-core
    • Labels:
      None

      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.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development