Its interesting to write this kind of posts about Tapestry community because it makes you realize that we’ve got a pretty active community.
Vox Wooki 2 will especially focus on TapesTwitter: an open source clone of Twitter powered by Tapestry.
TapesTwitter
Some weeks ago, Laurent Guerin and Katia Aresti have silently published an application named TapesTwitter on Github.
We decided to download it and see what this application can do. TapesTwitter is a modest clone of Twitter powered by Tapestry. The stated goal is to provide a demonstration application to show what Tapestry is capable of. And that’s precisely what we liked about this application. A newcomer will find all necessary elements to get started with Tapestry : components and mixins, overrides of specific Tapestry behaviors like AJAX validators, integration of spring-security, i18n etc.

Custom Ajax validators

Internationalisation

One of their exclusives components: letters count system
Congratulations Laurent and Katia for your job, I’m convinced that it will be useful for a lot of people. I strongly encourage tapestry users to take a look at it.
Contributions
Geoff Callender continues to update Tapestry Jumpstart. Not less than two releases of Jumpstart have been made since last Vox Wooki. Theses releases focus on validators and there is an interesting AJAX validator implementation. I always recommend people to bookmark Jumpstart when I give Tapestry trainings: this application is the best cookbook for Tapestry I know.
Kalle Korhonen from Tynamo also announced the availability of tapestry-security 0.2.0. This contribution is an integration of Apache Shiro security framework (previously known as JSecurity), which is, as far as I know, a pretty good tool!
Other news from the community
Igor Drobiazko announced that his german written book on Tapestry 5 will be translated in English. This is really great and I hope that the english edition will be revisited to cover the new Tapestry 5.2 API.
Finally, Tapestry official logo and website have both been redesigned. I’m largely implicated on this but it’s also interesting to notice that these proposals have been discussed on tapestry developer mailing list. The community had the opportunity to be implicated by providing feedback, and I think it’s a good way of doing things.

