I suppose you could use Clojure for back end logic that is traditionally implemented as IoC services. Using proxy and/or genclass, you might even be able to have Clojure functions be the implementation of service interfaces.
If you are saying "can I implement pages and components in Clojure" I would say that is a signficant dead-end. Clojure is about avoiding state, Tapestry is about embracing state. Also check out http://github.com/hlship/cascade On Sat, Oct 31, 2009 at 2:53 AM, Sergey Didenko <sergey.dide...@gmail.com> wrote: > Can anyone advise best practices on using Tapestry 5 with Clojure? > > Tapestry 5 is a good choice if I want to use Clojure widely, isn't it? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
