Tapestry Training -- From The Source

Let me help you get your team up to speed in Tapestry ... fast. Visit howardlewisship.com for details on training, mentoring and support!

Tuesday, April 15, 2008

A round-up of Tapestry blogs

I was just fiddling with Google's Blog Search and searched for "java tapestry"; here's a few things I stumbled upon:

Fun stuff ... and I have more advancements for Tapestry 5 about ready to announce!


Jaime said...

I have read Alexander's book and It is a good one but I think we need one book that takes a deeper look into tapestry. The things that I have seen on tapestry 5 are really great, saving a lot of time developing application. I have done 2 small applications.

I am starting a new project but is going to be a big one, (a small team, from 3 to 4 people but will take more than a year the hole project. Of course with partial releases) and I am convincing them to use Tapestry (well, :|, I have the final word there, I am going to be in charge of the project), but need better documentation.

I liked what Kent Tong did with his book on Tapestry 4, Unfortunately he is no more writing on Tapestry 5 but Wicket and JSF.

Jaime said...

I am starting to migrate to Tapestry 5. I have a couple of application done with Tapestry 4 which I think I will keep them on Tapestry 4.

Those applications are really small ones, so I do not really worry to change them or not to Tapestry 5. Now, I am starting a new project, but this is a big one and for a big government Institution.

I am the one who have to decide the technology to use. I have read about Grails, Wicket, Struts 2 and Tapestry 5. Well, On my opinion Tapestry 5 is easier and faster to develop in but, to be honest, because of the kind of client I am not sure If I should use Tapestry or JSF (you know, this kind of gays always think on standards and not on the best solutions).

The thing is that I won't like that a migration from Tapestry 5 to Tapestry 6 to be as hard as from Tapestry 4 to Tapestry 5. I, as a developer, understand that, well, why trying to keep blackward compatibility when I can do a really big improvement If I do not do that ?. But, well, as a project manager one could think, why choosing a framework that when there is a new release I will be, as Kent said, stuck with the previous one ?.

It is not an easy decision sometimes, but, well, there are a lot of development done on Struts 1. I think that really few people will choose Struts 1 for a new project and, as far as I know, there is no direct way to migrate an application from Struts 1 to Struts 2. On the other hand, Struts 1 kept on the market a lot of years, and it is still on development. Tapestry have had a lot of changes on the same years.

The way that tapestry 5 was developed spouse that, on future releases it will be backward compatible. At least that what the tapestry home page says :D. I hope this to be true so I can really bet to use tapestry on this project. (And of course, we need a book that fully covers tapestry 5. Alexander's book is good but not take a deeper look into tapestry 5).

by the way, my English is not really good so I hope I could explain my self.


Howard said...

Jaime -- I wouldn't worry, Tapestry 6 is not something to worry about. Tapestry 5 is it. It's fresh, elegant and designed from scratch to support future extensions without sacrificing backwards compatibility.