> From: Daniel Rall <[EMAIL PROTECTED]> >> Scott Eade <[EMAIL PROTECTED]> writes: >> The default TR.props in tdk 2.1 includes the configuration of a >> ClasspathResourceLoader for loading Velocity templates from a jar file in >> WEB-INF/lib. >> >> I've been trying to make this work with Turbine but the starting directory >> to include in the jar file is not obvious and I have unfortunately been >> unable to get it to work so far (I have tried the templates directory and >> the screens directory). >> >> Has anyone managed to get this working? > > Hey Scott. I'm using an extension to Veocity's > ClasspathResourceLoader in Eyebrowse <http://eyebrowse.tigris.org/>. > Not directly applicable, but might be of help to see a working > example. Tigris has CVSWeb, so you can browse the source online if > you like. > > Dan
Thanks Dan. Eyebrowse uses Velocity without Turbine. I think the use of ClasspathResourceLoader (or the extension used in Eyebrowse) with straight Velocity is tried and tested. Turbine however has the added complication of the directory structure (email, layouts, navigations, screens) that I am not certain is dealt with anywhere. Given the lack of response am I to assume that nobody is using the default ClasspathResourceLoader that is configured in TurbineResources.properties? Cheers, Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
