[
https://issues.apache.org/jira/browse/TAPESTRY-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498397
]
Andreas Andreou commented on TAPESTRY-1179:
-------------------------------------------
I don't see this happening - even though i dont exactly remember the original
reasoning for the naming.
You can always have your own empty If class, like
public abstract class If extends IfBean {}
and use that in your own project.
> practical component class naming for For, If and Else
> -----------------------------------------------------
>
> Key: TAPESTRY-1179
> URL: https://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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
