>Is it correct that the AppModule methods are static or > is the recommend way to make them non static. Both seems to work. For the most part, static is the correct approach
regards, Peter ----- Original Message ----- From: "Sebastian Hennebrueder" <use...@laliluna.de> To: "Tapestry users" <users@tapestry.apache.org> Sent: Thursday, 6 August, 2009 17:35:38 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Custom validation for @Validate Hello, while describing the validation mechanism of Tapestry in my article, I used my findings to update the Wiki. http://wiki.apache.org/tapestry/CreatingCustomValidators Could someone please review it, as I am not experienced with Tapestry. Is it correct that the AppModule methods are static or is the recommend way to make them non static. Both seems to work. Personally, I believe that this information belongs to the normal documentation and not the Wiki. I checked the Validation page but it is already to large. What do you think about refactoring the guide documentation and moving all custom extension docs to a dedicated group? This would leave the doc shorter for standard users and give still a quick pointer for people customizing their Tapestry appl -- Best Regards / Viele Grüße Sebastian Hennebrueder ----- Software Developer and Trainer for Hibernate / Java Persistence http://www.laliluna.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
