[ https://issues.apache.org/jira/browse/TAP5-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Harner updated TAP5-1381: ----------------------------- Affects Version/s: 5.4 > Page lifecycle documentation: What is called and when > ----------------------------------------------------- > > Key: TAP5-1381 > URL: https://issues.apache.org/jira/browse/TAP5-1381 > Project: Tapestry 5 > Issue Type: Improvement > Components: documentation > Affects Versions: 5.4 > Reporter: Borut Bolcina > > At http://tapestry.apache.org/page-life-cycle.html the documentation about > page lifecycle can be improved. It should be more clear to developers what is > called and when. Maybe a diagram and short explanations along with good > practices what to put in each event method would be in order. > Geoff has made a good effort at > http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen > and the logging of log4j.category.tapestry.events.com.acme.pages=debug can > give clues, but I think the lifecycle is so crucial it should be explained in > more detail. > Also, the link in the sentence "As with component rendering, you have the > ability to make your components "aware" of these events by identifying > methods to be invoked." is broken. -- This message was sent by Atlassian JIRA (v6.2#6252)