[
https://issues.apache.org/jira/browse/TAP5-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Marx updated TAP5-1281:
------------------------------
This was just an example....of a small website with only a couple of queries.
Of course there could be more services, or one per entity...some kind of
injection.
nameOfServcie:method - using the old convention over configuration as a
replacement for and empty class with a single @Inject NameOfService
nameOfService annotation.
When looking at the way Tapestry5 has gone from Tapestry4, it could be a new
direction. At the beginning we had BaseComponent and BasePage...later this was
a simply Pojo...and maybe the next step is to even work without component and
page specific classes....just with services.
Should I post this to the maiing list, or do you think it's useless?
> Simplifications for lightweight Tapestry5 projects
> --------------------------------------------------
>
> Key: TAP5-1281
> URL: https://issues.apache.org/jira/browse/TAP5-1281
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Tobias Marx
> Priority: Minor
>
> In order to simplify Tapestry5 even further i would like to suggest the
> following:
> - auto-creation of "empty" page and component classes if they don't exist at
> runtime (to reduce number of lines of code, especially for small projects &
> demos)
> - being able to reference a "global" service by default from within the
> templates where all database queries / persistence queries can be placed
> This way, you could create quite complex web applications with only a few
> files:
> - a layout templates
> - x template files for all pages (instead of 2*x)
> - y template files for all components (instead of 2*y)
> - one "global" service as an additional file that contains all
> hibernate/persistance queries
> This would cater of all users that want to create lightweight websites with
> only as many lines of code/files as really needed.
> A lot of website can be implemented just by querying data and displaying
> them in a template (loop)
> The idea:
> - reduce the lines of code for small / medium projects
> - create even more convincing Tapestry demos (vs. RoR/PHP)
> - increase acceptance by more users checking Tapestry out for the first time
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
