We are hoping to use Tapestry 4.0 in a production site to release next year. I've looked over the bug list, and only found a few issues that affect our site that I think must be fixed for the 4.0 release:
1) Checkboxes & FieldLabels (TAPESTRY-672/652/517): We've had to modify our UI design because you can't put the FieldLabel after the Checkbox. Even if it's a hack, you can't ship a framework that doesn't support this very common UI style. 2) Cookie handling (TAPESTRY-571/438/419): Right now the CookieSource is crippled, and we've had to provide our own service and implementation so that our site can set permanent cookies or session cookies as situations warrant. The CookieSource interface doesn't even allow this to be added with a different implementation. A web framework shouldn't require this kind of workaround to set permanent cookies. 3) FieldLabel rendering (TAPESTRY-694): Getting in the way of some of our UI plans. On performance, we're about to begin heavy-duty testing of some pieces of our code in our perf lab, and I have some tests of raw Tapestry page rendering planned, as well as with our biz logic hooked up via Spring. I will report what findings I can to the list, but don't expect anything for a few weeks. Overall, we're happy with our decision to use Tapestry, assuming that it hold up in our perf testing. We've got a lot of suggestions for 4.1, but I'll hold those for a later time. jeff -----Original Message----- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Sunday, October 16, 2005 8:24 AM To: Tapestry development Subject: Getting to 4.0 end game I believe we are getting very close to the 4.0 end game. I still have a few bugs I really want to fix, and some more documentation and tutorials that *should* get written. But nothing that can't wait for a 4.0.1 bug fix release or a 4.1 release. I would encourage developers to take a look at the open bug list and see what's pending. How many people are using 4.0 in a production environment right now? Or ramping up to a production environment? My biggest concern is runtime performance. My gut feeling is that outside of startup time, 4.0 is equal to or better performing than 3.0. I've been troubled by some concerns on the web about memory leeks possibly related to Javassist class creation (but I suspect those people are running with caching disabled and just don't know it, or won't admit it). I'm hoping that beta-12 will be the last beta, and we can call a vote for a release candidate after that. However, release working software is more important than keeping to a schedule. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- 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]
