That depends entirely on your requirements. The API for tap 4.1.x is still not entirely stable (or wasn't last time I checked, anyway, and I assume that the fact that it isn't the recommended release is confirmation of this), so not only are you still likely to encounter bugs, but there is also no guarantee that you won't have to modify code to upgrade your version to the latest 4.1.x release. This is more an issue for some teams than for others. Tap 4.0.x does support ajax functionality, via the tacos component library, which provided much of the insipration for the tap 4.1 ajax mechanism. So if you want a stable codebase, you can definitely opt ofr Tap 4.0 + tacos 4.0. Given the differences that will arise between tap 5.x and tap 4.1, I am just waiting for tap 5.x. It doesn't look as though there will be any backwards compatibility from 4.1 to 5, so I am just going to skip the 4.1 release and get maximum return on my upgrade investment by going straight to 5.x once it is ready. It is definitely lacking in much necessary functionality right now including, I believe, any mechanism for doing ajax-type requests. So I definitely don't recommend 5.x, but the choice of whether to go with 4.0 or 4.1 is dependent upon your requirements with regard to stability.
--sam On 4/25/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
Over the last year, we have slowly been converting an internal application from a home brewed infrastructure to Tapestry 4.0. Some of the new functionality we need to add would best be handled with Ajax and I so I started looking at the newer versions of Tapestry. I can't seem to figure out which version of Tapestry I should upgrade to. The "official distribution" page lists Tapestry 4.0.2 as the latest stable build. This version doesn't support Ajax to the best of my knowledge. Folks using Maven2 seem to be encouraged to use the 4.1.2-SNAPSHOT. Is it stable enough to be used in a production environment? Is it really a good idea? Is there an "official distribution" of 4.1.0 or 4.1.1 I should consider? Reading the e-mail list, I see a lot of people using Tapestry 5.0.3. Is there enough functionality ready for me to consider it? I assume this will be the longest migration path for us, but since I need to upgrade, if now is the time, so be it. Thank you in advance for any help. Tony Nelson Starpoint Solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
