You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Seth Call (JIRA)" <ji...@apache.org> on 2009/06/05 00:23:07 UTC
[jira] Created: (TAP5-739) Allow recursion of a component within
itself
Allow recursion of a component within itself
--------------------------------------------
Key: TAP5-739
URL: https://issues.apache.org/jira/browse/TAP5-739
Project: Tapestry 5
Issue Type: New Feature
Reporter: Seth Call
Ideally, Tapestry would allow a component to be nested within itself.
Because recursion of a component within itself is not possible, it is very difficult to represent a tree structure, which a component representing each node of the tree.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-739) Allow recursion of a component within
itself
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo closed TAP5-739.
----------------------------------------------
Resolution: Won't Fix
This can't be implemented in Tapestry without rewriting it from scratch. Read the "Principle 1 -- Static Structure, Dynamic Behavior" section of http://tapestry.apache.org/tapestry5.1/ to know why. Summary: Tapestry has a static tree of components, and allowing recursion in templates needs dynamic instantiation of components.
By the way, it's not hard to render trees or tree-like structures inside a component: just render everything in code. One example: http://ars-machina.svn.sourceforge.net/viewvc/ars-machina/tapestry-crud/branches/1.1/src/main/java/br/com/arsmachina/tapestrycrud/components/TreeSelect.java?revision=595&view=markup.
> Allow recursion of a component within itself
> --------------------------------------------
>
> Key: TAP5-739
> URL: https://issues.apache.org/jira/browse/TAP5-739
> Project: Tapestry 5
> Issue Type: New Feature
> Reporter: Seth Call
>
> Ideally, Tapestry would allow a component to be nested within itself.
> Because recursion of a component within itself is not possible, it is very difficult to represent a tree structure, which a component representing each node of the tree.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-739) Allow recursion of a component within
itself
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo closed TAP5-739.
----------------------------------------------
Resolution: Won't Fix
This can't be implemented in Tapestry without rewriting it from scratch. Read the "Principle 1 -- Static Structure, Dynamic Behavior" section of http://tapestry.apache.org/tapestry5.1/ to know why. Summary: Tapestry has a static tree of components, and allowing recursion in templates needs dynamic instantiation of components.
By the way, it's not hard to render trees or tree-like structures inside a component: just render everything in code. One example: http://ars-machina.svn.sourceforge.net/viewvc/ars-machina/tapestry-crud/branches/1.1/src/main/java/br/com/arsmachina/tapestrycrud/components/TreeSelect.java?revision=595&view=markup.
> Allow recursion of a component within itself
> --------------------------------------------
>
> Key: TAP5-739
> URL: https://issues.apache.org/jira/browse/TAP5-739
> Project: Tapestry 5
> Issue Type: New Feature
> Reporter: Seth Call
>
> Ideally, Tapestry would allow a component to be nested within itself.
> Because recursion of a component within itself is not possible, it is very difficult to represent a tree structure, which a component representing each node of the tree.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.