all, In our project, I'm using VelocityServlet for the generation of our website, and VelocityEngine for generation of other stuff, mainly e-mails but there's SOAP-related stuff as well.
VelocityServlet runs within a modified Jo! which runs inside a forked Avalon Phoenix. VelocityEngine runs as a block within an Avalon .sar application. Templates, xml documents and other data are all retrieved from a database (firebird), cached, stored in JNDI (another avalon .sar takes care of that), and accessed by both engine and servlet to create our output. Works remarkably well (hurray for all!). What we currently do is push a DOM node into the context and get stuff from there (ie anakia-style). The DOM generation is currently our bottleneck (documents go from 5k to 5mb); it is also very annoying to use within templates for complex documents. One alternative would be to use commons digester or a similar package we have here in-house. The other alternative is to move to DVSL. This is just some background because you might enjoy hearing it, now for 2 main questions: - are there perfomance figures for DVSL? (I assume it's faster than xalan; anyone know how it compares to anakia?) - how stable is DVSL? (Is a release planned? If so, when?) thanks guys! - Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
