|
From: <jue...@we...> - 2004-07-19 12:20:35
|
> I meant to raise this when I generalised the behaviour of them but it > slipped my mind. They should be moved to a non-tag specific package = now. OK, I'll move them to "servlet.support" tonight, alongside = RequestContext. I'll also check whether Tomcat and Resin recompile JSPs = if a TLD has changed; else, the working directory needs to be scratched = to force a recompile. > VelocityConfigurer (and respective FreeMarkerConfigurer) ensure a > SpringResourceLoader is available for use, possibly in addition to any > other resource loading strategy in the case of FreeMarker. Does this = not > cover requirements? I'm a little unclear on what's missing here.. I've gone through the code Tuesday night last week; I need to recheck = what I actually noticed there. I'll do so when I'm back at home. (I'm = currently at the werk3 office.) > I'd intended contacting Seth again to catch up on this and ensure a > consistent approach for the three technologies. My feeling is that it > should be fairly quick to add given the basic framework code is OK for > resource loading, but I've not really looked closely at it yet. No problem - let's add those for 1.1 final or even 1.1.1, whenever they = are ready. Do you in principle envisage copying Velocity/FreeMarker = macros to the user's resource loader path, to allow for easy = customization? Juergne |