Rather than the enterprise I've been curious about frameworks for small medium size applications and websites and so I am looking at Velocity as it seems to have much less overhead than frameworks like Struts or Taperstry...
I use velocity extensively with Struts, and as Gregg said it's a view technology rather than a framework itself.
We use Velocity for email template generation as well as normal pages instead of JSP. IMHO, Velocity is much simpler as compared to JSP pages and moreover it's so basic that it forces you to keeep all business logic out of it, in a way a better view technology because at times one is tempted to push some logic in JSP. In Velocity it really gets as siple as some HTML + few $variable_names with minimal presentation logic. I think it gets much simpler for designers to work on Velocity templates as well.
The only grumble from my side is perhaps lack of info/articles on Velocity's usage. If I get time, I am planning to put together some info/chapters online.
velocity has links to articles and the docs are'nt bad either. and there is a nice book on velocity too.
Didn't know about this book, don't know if it's available in India or not.
As or docs, lot of things are not documented (esp in velocity+dtruts) and few documented things from user guide don't work yet - like map creation/initialization syntax(unless you want to take nightly builds from velocity, our processes don't allow us to do that for our release projects).