[
https://issues.apache.org/jira/browse/TAP5-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-237.
-------------------------------------
Resolution: Duplicate
Assignee: Howard M. Lewis Ship
The Dynamic component was moved from tapx-core to tapestry-core as part of 5.3.
> Add support for skinnability via a dynamic layout component
> -----------------------------------------------------------
>
> Key: TAP5-237
> URL: https://issues.apache.org/jira/browse/TAP5-237
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Working with a client, we've come up with an excellent plan for a component
> that supplies dynamic content via a non-Tapestry XHTML template.
> Essentially, the DynaComponent (temporary name) reads and parses a
> well-formed XML file. Within the XML file, certain elements will be replaced
> with parameter Blocks to the DynaComponent.
> Assuming that the parsed XML templates can be cached efficiently (as a kind
> of token stream, ala Tapestry's internal representation of a parsed component
> template) this could work quite efficiently.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
