Hello, I am a little bit at a loss concerning the following case and hopefully not missed the whole point, but:
If I would like to integrate another templating mechanism (e.g. Jade) instead of or parallel to e.g. Velocity, where would I start? (not that I actually would do this right now, but just in case).. There is an old Howto (Template Service) mentioned in the Fulcrum project webpage*, and another template related link**; in the VCS/SVN I find a copy of JSP and Velocity Service (fulcrum-template) - but these classes (package org.apache.fulcrum.template) have sister classes e.g. in package org/apache/turbine/services/velocity in the default turbine module (AND the latter classes are more up-to-date, e.g. TurbineTemplateService compared to the same class in the other package). It seems to me, that integration of the templating mechanism as a Yaafi component is not the way to go... Was it a design decision in the past, NOT to integrate the templating services into Yaafi? Then may be IMO fulcrum-template should be removed (may be I missed the right place). So, my question is: Would I hook in the existing (Yaafi) component fulcrum-template (I do not use it at the moment) or just better look at the classes in package org.apache.turbine.services? Thanks, Georg * http://turbine.apache.org/fulcrum/howto/template-service.html ** http://turbine.apache.org/fulcrum/fulcrum-template, which currently points to the BSF component. BTW: The example shows, how it would be used as a fulcrum-yaafi, but I cannot find the class TurbineBSFService only DefaultBSFService. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
