[
https://issues.apache.org/jira/browse/TAP5-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago H. de Paula Figueiredo closed TAP5-1275.
-----------------------------------------------
Resolution: Won't Fix
Having a class per page is one Tapestry architectural decision that was done
after analyzing Tapestry 4, which had it. It only increased complexity and made
learning Tapestry more complex, not simpler
> Avoiding empty component classes
> --------------------------------
>
> Key: TAP5-1275
> URL: https://issues.apache.org/jira/browse/TAP5-1275
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2.0, 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4,
> 5.1.0.5, 5.1.0.6, 5.1.0.7, 5.0.15, 5.0.16, 5.0.17, 5.0.18, 5.0.19
> Reporter: Toby
> Priority: Minor
>
> Even when a component does not require any additional logic, an empty
> component class is still needed.
> It would be good if component classes are optional. Ideally you could just
> create component templates and use them directly without having to create
> empty component classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
