You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Norbert Sándor (JIRA)" <ta...@jakarta.apache.org> on 2006/12/09 21:31:20 UTC

[jira] Created: (TAPESTRY-1179) practical component class naming for For, If and Else

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


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


[jira] Commented: (TAPESTRY-1179) practical component class naming for For, If and Else

Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
    [ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1179) practical component class naming for For, If and Else

Posted by "Norbert Sándor (JIRA)" <de...@tapestry.apache.org>.
    [ https://issues.apache.org/jira/browse/TAPESTRY-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502785 ] 

Norbert Sándor commented on TAPESTRY-1179:
------------------------------------------

That's not the same because I have to copy-paste the original .jwc files and monitor the changes in them... forever :)

> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Resolved: (TAPESTRY-1179) practical component class naming for For, If and Else

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

Andreas Andreou resolved TAPESTRY-1179.
---------------------------------------

    Resolution: Won't Fix

> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Updated: (TAPESTRY-1179) practical component class naming for For, If and Else

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
     [ 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