You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org> on 2006/12/10 18:30:21 UTC
[jira] Updated: (TAPESTRY-1179) practical component class naming
for For, If and Else
[ http://issues.apache.org/jira/browse/TAPESTRY-1179?page=all ]
Jesse Kuhnert updated TAPESTRY-1179:
------------------------------------
Fix Version/s: 4.1.2
> practical component class naming for For, If and Else
> -----------------------------------------------------
>
> Key: TAPESTRY-1179
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1179
> Project: Tapestry
> Issue Type: Bug
> Components: Framework
> Affects Versions: 4.1.1
> Reporter: Norbert Sándor
> Priority: Minor
> Fix For: 4.1.2
>
>
> Because @Component's type is not required anymore, it would be practical to rename ForBean, IfBean and ElseBean to For, If, Else accordingly.
> Regards,
> Norbi
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org