> We have quite a mess in the template service to accommodate > what I once thought would be a slew of templating engines. But really what > is happening is that most people are settling on Velocity or JSP (more on > JSP being a first class citizen later) and the abstraction that we have > isn't worth it IMO and it makes things far too complicated with the > ContextAdapters.
I'm very interested in hearing your thoughts on JSP as a first class citizen. As far as simplification, I agree completely, but want to emphasize that there will be other template mechanisms that are important to people (like JGenerator is to me). That said, it seems more important that turbine have high quality and easy to understand support for a couple of template systems (just velocity would make me happy =), rather than a super flexible interface for supporting any template engine out there. As long as it is not really difficult or impossible for me (as a user of turbine) to insert my own means of rendering templates, I will be happy. And to some extent, with the pipeline, everything can be replaced with enough work. > That being said I will apply your patch :-) Thanks! James -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
