On Wed, Sep 1, 2010 at 9:02 AM, White, Tim <tim.wh...@qwest.com> wrote: > Sure. We have 100k+ templates, and a massive setup to use the resource > loaders to pull things across from numerous locations. > > 90% of the time what we're pulling is Velocity templates, but the remaining > 10% is .js files and such that aren't valid velocity, so they break when we > try to load them....
can you use Engine 1.7-beta1? It has the textblock feature: #[[ this is included but not parsed, so you can put anything here ]]# which you can use to keep your javascript from breaking. of course, this still means a wee bit of parsing overhead and context construction. but if you are serving static files through the VVS, then i think you'll just have to live with that. it's designed only with dynamic files in mind, where #include is the extent of static support. > On Sep 1, 2010, at 9:56 AM, Nathan Bubna wrote: > >> Ick. Why run that stuff through the resource loaders at all? This is >> not really an intended usage of Velocity, so don't be too surprised >> that there isn't much (anything?) in the way of support for it. I >> can't currently think of any way to do this via the VVS that doesn't >> involve hacking a custom build of Velocity. > > > This communication is the property of Qwest and may contain confidential or > privileged information. Unauthorized use of this communication is strictly > prohibited and may be unlawful. If you have received this communication > in error, please immediately notify the sender by reply e-mail and destroy > all copies of the communication and any attachments. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > For additional commands, e-mail: user-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
