You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/12/13 20:26:43 UTC

[jira] Created: (TAPESTRY-1975) Template parser is insufficiently picky about component ids

Template parser is insufficiently picky about component ids
-----------------------------------------------------------

                 Key: TAPESTRY-1975
                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1975
             Project: Tapestry
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.0.6
            Reporter: Howard M. Lewis Ship


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Closed: (TAPESTRY-1975) Template parser is insufficiently picky about component ids

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-1975.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.7

> Template parser is insufficiently picky about component ids
> -----------------------------------------------------------
>
>                 Key: TAPESTRY-1975
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1975
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.0.7
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Assigned: (TAPESTRY-1975) Template parser is insufficiently picky about component ids

Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
     [ https://issues.apache.org/jira/browse/TAPESTRY-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship reassigned TAPESTRY-1975:
----------------------------------------------

    Assignee: Howard M. Lewis Ship

> Template parser is insufficiently picky about component ids
> -----------------------------------------------------------
>
>                 Key: TAPESTRY-1975
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1975
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org