Tim Colson said: > > as you may have noticed, i checked in a bunch of changes > Nice to have you back. School and work must have slowed down? ;-)
heh. work slowed down for a little bit. but i'm still drowning in schoolwork and probably won't really surface again for a month or two. > > tonight to convert > > the VelocityView and VelocityStruts servlets and tools from > > singleton mode to the use of a VelocityEngine. > Break it down for those of us who are Stupid (ok -- just me I suppose)... > what does this change mean at a high-level to dudes like me? What will > happen? a. not much. for instance, i didn't have to change a thing in the example apps we ship. they worked with the changes just fine. b. log output from tools and their managing classes will not all be spewed into the ServletLogger by default anymore. only the VVS and VLS will still do this by default (you can, of course, still configure them to do otherwise in your velocity.properties), because they have direct access to the VelocityEngine being used and can thus use its LogSystem. if you want the rest of VelocityView and/or VelocityStruts to have their log output shipped into the configured LogSystem for the VVS/VLS, then you will have to configure commons-logging for your app to use the LogSystemCommonsLog. c. you can use several different instances or subclasses of VelocityViewServlet in the same web application and give them each different velocity.properties configurations. d. similar to point c., you can use the VVS alongside other servlets or software that uses the singleton without conflict between them (e.g. Turbine). and there's probably other ramifications that are presently escaping my brain, but hopefully this helps a bit. :) Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
