Is 2.0 relatively backward-compatible with 1.4? I wish I could have a
software release that only dealt with library upgrades. Mmmm... that'd
be nice.
yes, i worked pretty hard to maintain a significant level of
compatibility for 2.0, to give people some time to change before 2.1
starts stripping out the B.C. stuff.
I can confirm this, Nathan did a great job about B.C.
There are some gotchas of course ; I can think of:
- servlets that inherit VelocityViewServlet often need to be reviewed
- custom tools that rely on receiving a ServletContext as init() param
need to be updated (the proper way is now to have a public
setServletContext() method)
- tools instantiation is lazier than before, this is a good
optimization but can lead to some side-effects
Please tell us which difficulties you encountered, it can be worth
enumerating all potential problems for other users.
Don't miss:
http://velocity.apache.org/tools/releases/2.0/creatingtools.html#Standard_Tool_Properties
and http://velocity.apache.org/tools/releases/2.0/summary.html
Claude
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org
