At the beginning of this week I was in Franskfurt for a Cocoon get together. Apart from some great talk&beer, I was enlightened by Nicola Ken (of Forrest, Cocoon, and whatever-comes-to-his-mind fame :-)) about Jetty, a servlet engine that he set up for both Forrest and Cocoon in the past few weeks.


Whith his help I have now a running setup with impressive result. Jetty is a fast and small (~700KB) servlet engine which can be easily embedded. As of now I have an Ant task that fires up my Xindice DB&XML-RPC server in seconds, instead of going trough the usual Tomcat "deploy and have a coffee" crap, which makes me *much* more productive.

Not only that: with Jelly embedded, the source tree is again self-hosting, with no dependencies on external apps, meaning that it would be trivial for users to start the database (yeah!), and for developers to write unit tests against the XML-RPC driver.

So now for the proposal: is it OK to you if I commit the Jetty support in CVS? We grow by 700KB, but we gain IMHO a hell of a lot in flexibility.

LMK,

--
Gianugo



Reply via email to