You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Chris Mylonas (JIRA)" <ji...@apache.org> on 2013/10/28 23:48:32 UTC

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

Chris Mylonas created TAP5-2210:
-----------------------------------

             Summary: 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.1#6144)