You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/08/01 20:55:38 UTC

[jira] [Closed] (TAP5-2210) Other ways of using tapestry (e.g. disable service reloading)

     [ https://issues.apache.org/jira/browse/TAP5-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-2210.
--------------------------------------

    Resolution: Won't Fix

If you wish to help with documentation, please file a CLA with Apache and get in contact with us to enable write access to the documentation wiki.

> Other ways of using tapestry (e.g. disable service reloading)
> -------------------------------------------------------------
>
>                 Key: TAP5-2210
>                 URL: https://issues.apache.org/jira/browse/TAP5-2210
>             Project: Tapestry 5
>          Issue Type: Documentation
>          Components: documentation
>    Affects Versions: 5.3.7
>            Reporter: Chris Mylonas
>            Priority: Minor
>
> Perhaps to save many people's time on the mailing list and dev - something like an "alternatives" section in the docs for some of tapestry's features.
> Personally, I'm looking at tapestry for a 3rd time in the last few years for a project and finally getting into the guts of it.
> e.g.
> Service Implementation Reloading
> There was this thread - http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Switching-off-Reloading-of-Service-Implemenation-td5724115.html  which a simple "Alternative" section in the docs could have saved a few man-hours.



--
This message was sent by Atlassian JIRA
(v6.2#6252)