hi jonathan, 1) you can use either way. some methods must be static: binder() and contributeAlias. by using static methods you can avoid circular dependencies
2) the XXX refers to the service name. the implementation of that service can hav the follownig parameters Collection -> maps to Configuration List -> maps to OrderedConfiguration Map -> maps to MappedConfiguration ... so the service decides how he expects the contribution 3) yes, "decorate" for decorating services. 5.1.0.0-SNAPSHOT also comes with a "advice" prefix its all documented, but scattered in several documents. g, kris Jonathan O'Connor <ninki...@eircom.net> 13.02.2009 14:38 Bitte antworten an "Tapestry users" <users@tapestry.apache.org> An Tapestry users <users@tapestry.apache.org> Kopie Thema AppModule conventions Hi, I've been looking for documentation about how the AppModule class works. Sadly, I have only found a few examples of bind/contribute and build methods, but nothing that explains when and what to use. I would like to know: 1. Which methods should be static and which non-static? Does it matter? 2. If I write a method "contributeXXX()" what does the XXX refer to? A Service? Also, why do some contribute methods take a Map, and others a list? Who decides? 3. Are there other prefixes that are magic, apart from bind, contribute and build? If I missed this in the standard documentation, then apologies, and a link to where to look is fine, Jonathan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
