We use Tapestry in prod since alpha-3... we use lots of memory because of big database caches, big it doesn't seems that Tapestry either had memory leak. As I said a long time ago, the transition was not painful, except for services, which needed lots of rewrite but... that's so much cleaner than before ;)
We really enjoy Tapestry 4.0, event from those early alphas, so *real* *big* thanks for all the work done by the community. Also, we are working on XUL support for Tapestry (4.0), we'll release that open-sourced (GPL? LGPL? ASL? BSD?) for sure ;) We hope that it will help Tapestry in reaching the rich-web-client bright futur ;) Mikael. Le dimanche 16 octobre 2005 à 11:24 -0400, Howard Lewis Ship a écrit : > 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]
