velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Bubna" <nbu...@gmail.com>
Subject Re: Upgrade to velocity 1.5 - a few questions
Date Tue, 12 Jun 2007 16:01:53 GMT
On 6/11/07, Peter Locke <plocke@abebooks.com> wrote:
> I would like to upgrade to velocity 1.5 from 1.4 and take advantage of the
> fixes and improvements.   I have a few questions:
>
> 1) I would like to remove the now deprecated VelocityServlet, however the
> size and scope of our webapp and the number of different servlets extending
> VelocityServlet means it would be impossible to migrate everything to the
> recommended structure of VelocityViewServlet.   Is it possible to extend
> VelocityViewServlet instead of VelocityServlet with no (or minimal) ripple
> impact to the subclasses?  If not what is the recommended approach?

yeah, it should be pretty trivial.  ideally you should be able to just
change them from extending VelocityServlet to extending
VelocityViewServlet. (potentially just a two line change.   there have
been a few things deprecated internally in VelocityServlet that the
VelocityViewServlet doesn't support (like the old "properties"
init-param key instead of "org.apache.velocity.properties"), but even
those should be pretty easy to upgrade.

please let us know if you run into any trouble.  i'd like this switch
to be as painless as reasonable for users.

> 2) Logging improvements - our webapp business level code logs to the
> underlying log system via apache commons logging - is it possible to have
> Velocity log to commons logging automatically also, or does this require a
> custom implementation of LogChute?

the CommonsLogLogChute will be in Velocity 1.6.  i just didn't think
to put it in 1.5, and no one else brought it up.   it should, however,
be fairly trivial for you to grab that class from the trunk (or i can
grab it for you), compile it in your app and use it with 1.5.  just a
matter of pointing to it in your velocity.properties.  and again, i'll
be happy to answer any questions about getting that done.

> 3) I notice that JDOM 1.0 is a dependency now.  We are still on beta9 - what
> would be the potential side effects of not upgrading?  Of course I'd like to
> upgrade to 1.0 but that may not be an option.
>
> thanks for your help.
>
> --
> Peter Locke
> Senior Engineer / Dev Lead
> www.abebooks.com <http://www.abebooks.com/>
>
> t: 250.412.3240
> f: 250.475-6014
> e: plocke@abebooks.com <mailto:plocke@abebooks.com>
> --
> P.S. I'm currently reading Rainbow Six
> <http://www.abebooks.com/servlet/SearchResults?bx=off&sts=t&ds=30&bi=0&an=Tom
> +Clancy&tn=Rainbow+Six>  by Tom Clancy
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Mime
View raw message