>> tapestry could benefit from a "rosetta stone" of the equivalent methods of >> doing the same thing. > > That's a good documentation suggestions . . . JIRA please? :) Usually, > Tapestry avoids to provide more than one way of doing the same thing. On the > other hand, sometimes the Tapestry flexibility and architecture ends up > providing alternatives.
Created fool! (MR T reference of course) https://issues.apache.org/jira/browse/TAP5-1894
